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.
Affected products
argoproj: argo workflows
References8
- github.com/argoproj/argo-workflows/security/advisories/GHSA-377… ExploitMitigationVendor Advisory
- github.com/argoproj/argo-workflows/security/advisories/GHSA-377… ExploitMitigationVendor Advisory
- github.com/argoproj/argo-workflows/commit/534f4ff1cbd86908e8ff7… Patch
- github.com/argoproj/argo-workflows/releases/tag/v3.7.14 Release Notes
- github.com/argoproj/argo-workflows/releases/tag/v4.0.5 Release Notes
- access.redhat.com/security/cve/CVE-2026-42296
- bugzilla.redhat.com/show_bug.cgi?id=2468446
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42296…
Metrics
- CVSS 3.1
-
8.1
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N - EPSS — exploit probability
- 0% percentile: 37 · as of 13 November 2026
- CWE
- CWE-863
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.