CVSS 4.0
8.2 highCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NHigh (8.2) in argoproj argo workflows. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/argoproj/argo-workflows/v3 3.7.14.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hgithub.com/argoproj/argo-workflows/v3 (Go): fixed in 3.7.14github.com/argoproj/argo-workflows/v4 (Go): fixed in 4.0.5Explain CVE-2026-42294 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-42294?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-42294?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-42294 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| argoproj:argo_workflows | before 3.7.14 |
| argoproj:argo_workflows | from 4.0.0 before 4.0.5 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-jcc8-g2q4-9fxq | Go | github.com/argoproj/argo-workflows/v3 | <3.7.14 | 3.7.14 |
| GHSA-jcc8-g2q4-9fxq | Go | github.com/argoproj/argo-workflows/v4 | >=4.0.0 <4.0.5 | 4.0.5 |
| GO-2026-5462 | Go | github.com/argoproj/argo-workflows | all versions | no fix published |
| GO-2026-5462 | Go | github.com/argoproj/argo-workflows/v2 | all versions | no fix published |
| GO-2026-5462 | Go | github.com/argoproj/argo-workflows/v3 | <3.7.14 | 3.7.14 |
| GO-2026-5462 | Go | github.com/argoproj/argo-workflows/v4 | >=4.0.0 <4.0.5 | 4.0.5 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.
Red Hat rates this Important.
Red Hat OpenShift AI ships Argo Workflows in Data Science Pipelines container images (odh-data-science-pipelines-argo-workflowcontroller-rhel9 and odh-data-science-pipelines-argo-argoexec-rhel9) on affected streams. These images bundle a vulnerable Argo Workflows version prior to upstream fix 3.7.14.
The webhook interceptor reads the entire HTTP request body into memory before authenticating the request or verifying its signature on the /api/v1/events/ endpoint. An unauthenticated remote attacker can submit an extremely large request body, causing excessive memory allocation and potentially an out-of-memory crash of the Argo Server, resulting in denial of service for workflow execution and API access.
Red Hat OpenShift AI engineering is expected to deliver updated container images built with Argo Workflows 3.7.14 or later (3.x line) or 4.0.5 or later (4.x line). Until updates are available, restrict network access to the Argo Server webhook endpoint and enforce request body size limits at the Ingress or load balancer layer as described in the mitigation field.
Upgrade Argo Workflows to version 3.7.14 or later (3.x line) or 4.0.5 or later (4.x line) in affected Red Hat OpenShift AI releases. Red Hat OpenShift AI engineering is expected to deliver updated Data Science Pipelines builds for affected streams (rhoai-2.25, rhoai-3.3, rhoai-3.4).
Until updated images are available, restrict network access to the Argo Server webhook endpoint (/api/v1/events/) using Ingress rules, firewall policies, or Kubernetes NetworkPolicy so only trusted webhook sources can reach it. Configure request body size limits at the Ingress or load balancer layer (for example, a maximum body size well below multi-gigabyte payloads) to reduce the risk of memory exhaustion from oversized requests.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift AI 3.3 | rhoai/odh-data-science-pipelines-argo-argoexec-rhel9:1790132012 | Fixed 2026-09-30 | RHSA-2026:73987 |
| Red Hat OpenShift AI 3.3 | rhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel9:1790130173 | Fixed 2026-09-30 | RHSA-2026:73987 |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-42294.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).