CVE-2026-54526Public exploitNetwork attack vector

Authenticated container execution via nested PodSpecPatch override

Published Jul 16, 2026 · Updated Jul 16, 2026

Improper access control in Argo Workflows before 3.7.15 and 4.0.0 through 4.0.5 allows remote authenticated users to run containers. ValidateUserOverrides and SanitizeUserWorkflowSpec allow ArtifactGC wholesale and pass its nested PodSpecPatch unchanged to ApplyPodSpecPatch. Exploitation requires Workflow creation rights, Strict or Secure template referencing, a referenced template with an output artifact, and OnWorkflowCompletion artifact garbage collection; the resulting pod can use an attacker-selected image, command, privileges, host networking, or hostPath mounts subject to cluster policy.

CVSS severity8.9
High
EPSS probability0.36%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper access control in Argo Workflows before 3.7.15 and 4.0.0 through 4.0.5 allows remote authenticated users to run containers. ValidateUserOverrides and SanitizeUserWorkflowSpec allow ArtifactGC wholesale and pass its nested PodSpecPatch unchanged to ApplyPodSpecPatch. Exploitation requires Workflow creation rights, Strict or Secure template referencing, a referenced template with an output artifact, and OnWorkflowCompletion artifact garbage collection; the resulting pod can use an attacker-selected image, command, privileges, host networking, or hostPath mounts subject to cluster policy.

The record

CVE
CVE-2026-54526
Published
Jul 16, 2026
Updated
Jul 16, 2026
Vendor
Argo Project
Product
Argo Workflows
Classifications
CWE-284, T1610
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 16, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 16, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 3.7.15
  2. Affected versionversion=>= 4.0.0, < 4.0.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Argo Project · Argo Workflowsversion=< 3.7.15; version=>= 4.0.0, < 4.0.6

Published CVSS scores

8.9GitHubCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-284Improper Access Control
T1610Deploy Container

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo