CVE-2026-42296: argoproj argo-workflows · Incorrect Authorization
Affects argoproj argo-workflowsSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 4.0.5 or 3.7.14 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.0.5, 3.7.14
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A: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
A fix for this vulnerability is available in Argo Workflows versions 3.7.14 and 4.0.5. Users should upgrade to these versions or later to remediate the issue. Additionally, Kubernetes clusters should enforce PodSecurity admission or use OPA/Gatekeeper policies to provide defense-in-depth. Since the vendor advisory does not specify alternative mitigations or indicate that no action is required, upgrading is the recommended 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, a user with create Workflow permission can bypass templateReferencing: Strict to get host network access, switch service accounts, override pod security context, add tolerations to schedule on control-plane nodes, or enable SA token mounting. This defeats the stated purpose of the feature. The practical impact depends on what Kubernetes-level controls are in place. Clusters with PodSecurity admission or OPA/Gatekeeper would independently block some of these (like hostNetwork). Clusters that rely on Argo's Strict mode as the primary enforcement layer are fully exposed. This issue has been patched in versions 3.7.14 and 4.0.5.
References
- github.com/argoproj/argo-workflows/security/advisories/GHSA-3775-99mw-8rp4 (opens in a new tab)
- github.com/argoproj/argo-workflows/commit/534f4ff1cbd86908e8ff76d97d553ad5a49a950d (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-42296 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2468446 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42296.json (opens in a new tab)