Impact
Argo Workflows is an open source container-native workflow engine for Kubernetes. From versions 2.9.0 to before 4.0.2 and 3.7.11, a user who can submit Workflows can bypass all security settings defined in a WorkflowTemplate by including a podSpecPatch field in their Workflow submission. The podSpecPatch field takes precedence over the referenced WorkflowTemplate during spec merging and is applied directly to the pod spec at creation time with no security validation, even when the controller operates in Strict mode. This allows an attacker to run arbitrary containers or privileged actions, effectively escalating privileges and compromising cluster security. This weakness is related to CWE‑807 (Privilege Escalation) and CWE‑863 (Missing Authorization).
Affected Systems
The affected vendor is argoproj:argo-workflows. Vulnerable releases include any version from 2.9.0 up to, but not including, 4.0.2, as well as any version up to, but not including, 3.7.11. The issue was fixed in release 4.0.2 and 3.7.11. Users should verify their installed version against these thresholds.
Risk and Exploitability
The CVSS score is 8.9, indicating high severity. EPSS score is below 1%, suggesting the likelihood of exploitation is currently low. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires the ability to submit a Workflow; hence any user with workflow-creation permissions can launch the attack. Once the podSpecPatch is applied, the attacker can modify pod specifications to run malicious containers, potentially gaining elevated privileges within the cluster. This vulnerability is therefore considered a high-risk privilege escalation vector for systems that have exposed workflow submission capabilities.
OpenCVE Enrichment
Github GHSA