CVE-2026-31892
Description
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From 2.9.0 to before 4.0.2 and 3.7.11, A user who can submit Workflows can completely bypass all security settings defined in a WorkflowTemplate by including a podSpecPatch field in their Workflow submission. This works even when the controller is configured with templateReferencing: Strict, which is specifically documented as a mechanism to restrict users to admin-approved templates. The podSpecPatch field on a submitted Workflow takes precedence over the referenced WorkflowTemplate during spec merging and is applied directly to the pod spec at creation time with no security validation. This vulnerability is fixed in 4.0.2 and 3.7.11.
How to fix
- argoproj argo_workflows3.7.11, 4.0.2 or later
- github.com/argoproj/argo-workflows/v44.0.2 or later
- github.com/argoproj/argo-workflows/v33.7.11 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| argoproj argo_workflows | 2.9.0 ≤ v < 3.7.11, 4.0.0 ≤ v < 4.0.2 | 3.7.11, 4.0.2 |
| github.com/argoproj/argo-workflows/v4Go | v < 4.0.2 | 4.0.2 |
| github.com/argoproj/argo-workflows/v3Go | v < 3.7.11 | 3.7.11 |
| github.com/argoproj/argo-workflowsGo | 2.9.0 ≤ v, No range specified | — |
| github.com/argoproj/argo-workflows/v2Go | 2.9.0 ≤ v | — |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.