What’s Vulnerable › Vulnerabilities

CVE-2026-31892: WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode

• Severity: high (CVSS 8.1 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.5% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2026-03-11 · updated 2026-07-15
• Weakness: CWE-863

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 products

• argoproj argo-workflows: from 2.9.0 before 3.7.11; from 4.0.0 before 4.0.2 — fixed in 3.7.11, 4.0.2

How to fix

Upgrade to a fixed version: argoproj argo-workflows 3.7.11, 4.0.2. Check the vendor advisory for mitigations.

References

• https://github.com/argoproj/argo-workflows/security/advisories/GHSA-3wf5-g532-rcrr
• https://access.redhat.com/errata/RHSA-2026:10184
• https://access.redhat.com/security/cve/CVE-2026-31892
• https://bugzilla.redhat.com/show_bug.cgi?id=2446551
• https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-31892.json

Get alerted when CVE-2026-31892 or the next vulnerability affects your stack