CVE-2026-31892
Argo Workflows is an open source container-native workflow engine …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/argoproj/argo-workflows/security/advisories/GHSA-3wf5-g532-rcrr
- nvd.nist.gov/vuln/detail/CVE-2026-31892
- github.com/advisories/GHSA-3wf5-g532-rcrr
- access.redhat.com/errata/RHSA-2026:10184
- access.redhat.com/security/cve/CVE-2026-31892
- bugzilla.redhat.com/show_bug.cgi?id=2446551
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-31892.json
- nvd.nist.gov/vuln/detail/CVE-2026-31892
- cve.org/CVERecord?id=CVE-2026-31892
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.