CVE-2026-31892 WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode
Attackers can bypass strict template security controls in Argo Workflows by injecting podSpecPatch, allowing unauthorized pod configuration changes.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-31892?
CVE-2026-31892 is a high-severity vulnerability in argoproj argo-workflows, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Which versions are affected by CVE-2026-31892?
11 open source packages ship an affected version, including github.com/argoproj/argo-workflows, argo-workflows and github.com/argoproj/argo-workflows/v2. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/argoproj/argo-workflows Go | All versions | None |
github.com/argoproj/argo-workflows Go | From 2.9.0 | None |
github.com/argoproj/argo-workflows Go | From 2.9.0 | None |
argo-workflows Bitnami | All versions | 3.7.11, 4.0.2 |
github.com/argoproj/argo-workflows/v2 Go | From 2.9.0 | None |
github.com/argoproj/argo-workflows/v3 Go | All versions | 3.7.11 |
5 more packages
github.com/argoproj/argo-workflows/v3 Go | All versions | 3.7.11 |
github.com/argoproj/argo-workflows/v3 Go | All versions | 3.7.11 |
github.com/argoproj/argo-workflows/v4 Go | All versions | 4.0.2 |
github.com/argoproj/argo-workflows/v4 Go | All versions | 4.0.2 |
github.com/argoproj/argo-workflows/v4 Go | All versions | 4.0.2 |
Products include Argoproj Argo Workflows.
How do I fix CVE-2026-31892?
Upgrade to a fixed version.
Is CVE-2026-31892 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31892 exists.
Other vulnerabilities in argoproj argo-workflows
- CVE-2026-28229 Argo Workflows has unauthorized access to Argo Workflows Template
- CVE-2026-54526 Argo Workflows: Incomplete fix for CVE-2026-31892: ArtifactGC.PodSpecPatch bypass of Strict/Secure templateReferencing
- CVE-2026-42295 Argo Workflows: Exposure of artifact repository credentials
- CVE-2026-42297 Argo Workflows Is Missing Authorization in Sync ConfigMap Provider
- CVE-2025-62157 Argo Workflows exposes artifact repository credentials in workflow-controller logs
Sources
Also known as BIT-argo-workflows-2026-31892, ECHO-11ce-20c3-b91e, GHSA-3wf5-g532-rcrr, GO-2026-4681, MINI-4g5j-fgcr-vv5p, MINI-7fmc-rh5x-78p7 and 7 more.