Skip to main content
VulnerabilityPublished Updated

CVE-2026-31892: argoproj argo-workflows · Incorrect Authorization

Affects argoproj argo-workflowsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.9 High : upgrade to 4.0.2 or 3.7.11 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
8.9High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.2, 3.7.11
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade argo-workflows and argoproj/argo-workflows to 4.0.2 or 3.7.11.

Affected software

ProductAffectedFixed in
argoprojargo-workflowsAffected
  • >=4.0.0 <4.0.2
Fixed in
  • 4.0.2
argoprojargo-workflowsAffected
  • >=2.9.0 <3.7.11
Fixed in
  • 3.7.11
GitHubargoproj/argo-workflowspkg:github/argoproj/argo-workflowsOther threatsAffected
  • <4.0.2 >=2.9.0
  • <3.7.11 >=3.7.0
Fixed in
  • 4.0.2
  • 3.7.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

An official fix is available. Users should upgrade to argoproj argo-workflows versions 4.0.2 or 3.7.11 or later to remediate this vulnerability. Until upgraded, restricting workflow submission permissions and monitoring for unusual podSpecPatch usage may reduce risk, but patching is the definitive mitigation.

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.

References

Community reviews

Loading reviews…