CVE-2026-54526
Argo Workflows allow-list bypass permits malicious podSpec injection (RCE/host compromise)
Is CVE-2026-54526 being exploited?
Not confirmed. CVE-2026-54526 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-54526?
CVE-2026-54526 is rated High with a CVSS score of 8.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54526?
Yes. A fix has been recorded for CVE-2026-54526. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54526 affect?
CVE-2026-54526 affects Argo Workflows < 3.7.15, Argo Workflows < 4.0.6, Kubernetes clusters running Argo Workflows, artifact-GC pods. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54526?
Upgrade to Argo 3.7.15 or 4.0.6; restrict Workflow/WorkflowTemplate submission rights.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows injection of strategic podSpec patches into artifact-GC pods enabling arbitrary image/command, privileged=true, hostPath/hostNetwork — leads to RCE and host/node compromise.
Immediate action required
- affected< 3.7.15
- affected>= 4.0.0 and < 4.0.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.