CVE-2026-42294: argoproj argo-workflows · Unthrottled Resource Allocation
Affects argoproj argo-workflowsSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 4.0.5 or 3.7.14 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.0.5, 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:NExploitation evidence
Disclosed: evidence found.
CVE published 9 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade argo-workflows to 4.0.5 or 3.7.14; argoproj/argo-workflows to 3.7.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| argoprojargo-workflows | Affected
| Fixed in
|
| argoprojargo-workflows | Affected
| Fixed in
|
GitHubargoproj/argo-workflowspkg:github/argoproj/argo-workflowsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is patched in Argo Workflows versions 3.7.14 and 4.0.5. Users should upgrade to at least these versions to remediate the issue. No vendor advisory indicates alternative mitigations or that no action is required. Patch status is confirmed by the vendor advisory. There is no indication that this is a cloud service with vendor-managed remediation.
Description
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.
References
- github.com/argoproj/argo-workflows/security/advisories/GHSA-jcc8-g2q4-9fxq (opens in a new tab)
- github.com/argoproj/argo-workflows/commit/7abb4de6c3599e2d5d960ba4d5de4cf1df109965 (opens in a new tab)
- github.com/argoproj/argo-workflows/releases/tag/v3.7.14 (opens in a new tab)
- github.com/argoproj/argo-workflows/releases/tag/v4.0.5 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-42294 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2468443 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42294.json (opens in a new tab)