Skip to main content
VulnerabilityPublished Updated

CVE-2026-42297: argoproj argo-workflows · Missing Authorization

Affects argoproj argo-workflowsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.5 High : upgrade to 4.0.5 soon.

Data as of 15 Nov 2026, 20:25 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 May 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 15 Nov 2026.

What to do

Upgrade argo-workflows and argoproj/argo-workflows to 4.0.5.

Affected software

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

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

AI-suggested

A fix is available in Argo Workflows version 4.0.5. Users should upgrade to version 4.0.5 or later to remediate this vulnerability. The Red Hat advisory confirms the patch availability. No additional mitigations or workarounds are specified in the advisory.

Description

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From version 4.0.0 to before version 4.0.5, the Sync Service's ConfigMap-backed provider (server/sync/sync_cm.go) performs zero authorization checks on all CRUD operations (create, read, update, delete). Any authenticated user — including those using fake Bearer tokens — can create, read, update, and delete Kubernetes ConfigMaps containing synchronization limits. This issue has been patched in version 4.0.5.

References

Community reviews

Loading reviews…