WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode
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.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
github.com/argoproj/argo-workflows/v4Go | < 4.0.2 | 4.0.2 |
github.com/argoproj/argo-workflows/v3Go | < 3.7.11 | 3.7.11 |
github.com/argoproj/argo-workflowsGo | >= 2.9.0 | — |
Affected products
1- Range: >= 4.0.0, < 4.0.2
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
3- github.com/advisories/GHSA-3wf5-g532-rcrrghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2026-31892ghsaADVISORY
- github.com/argoproj/argo-workflows/security/advisories/GHSA-3wf5-g532-rcrrghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.