CVE-2026-31892
Argoproj Argo Workflows broken access control
- Published11 Mar 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
- 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://github.com/argoproj/argo-workflows/security/advisories/GHSA-3wf5-g532-rcrr
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-31892.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-31892 being actively exploited?
CVE-2026-31892 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.65%.
How severe is CVE-2026-31892?
CVE-2026-31892 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.65% probability of exploitation.
Which products are affected by CVE-2026-31892?
Affected products include Argoproj Argo Workflows.
How do I fix CVE-2026-31892?
Upgrade affected software to a fixed version, for example Argoproj Argo Workflows 3.7.11 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-31892 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.