cve.bz

CVE-2026-42294 argoproj argo workflows

8.2 highExploit referenceEPSS 0.6%Fix available

High (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.

On this page
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to versions 3.7.14 and 4.0.5, the Webhook Interceptor loads the entire request body into memory before authenticating the request or verifying its signature. This occurs on the /api/v1/events/ endpoint, which is publicly accessible (albeit intended for webhooks). An attacker can send a request with an extremely large body (e.g., multiple gigabytes), causing the Argo Server to allocate excessive memory, potentially leading to an Out-Of-Memory (OOM) crash and denial of service. This issue has been patched in versions 3.7.14 and 4.0.5.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-05-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
argoproj:argo_workflowsbefore 3.7.14
argoproj:argo_workflowsfrom 4.0.0 before 4.0.5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jcc8-g2q4-9fxqGogithub.com/argoproj/argo-workflows/v3<3.7.143.7.14
GHSA-jcc8-g2q4-9fxqGogithub.com/argoproj/argo-workflows/v4>=4.0.0 <4.0.54.0.5
GO-2026-5462Gogithub.com/argoproj/argo-workflowsall versionsno fix published
GO-2026-5462Gogithub.com/argoproj/argo-workflows/v2all versionsno fix published
GO-2026-5462Gogithub.com/argoproj/argo-workflows/v3<3.7.143.7.14
GO-2026-5462Gogithub.com/argoproj/argo-workflows/v4>=4.0.0 <4.0.54.0.5

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-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

Red Hat rates this Important.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat OpenShift AI 3.3rhoai/odh-data-science-pipelines-argo-argoexec-rhel9:1790132012Fixed 2026-09-30RHSA-2026:73987
Red Hat OpenShift AI 3.3rhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel9:1790130173Fixed 2026-09-30RHSA-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.

Attack patterns (CAPEC)

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).

References

Check your stackJSON