Authenticated ConfigMap manipulation via missing authorization checks
Published May 9, 2026 · Updated May 9, 2026
Missing authorization in Argo Workflows 4.0.0 through 4.0.4 allows remote authenticated users to manipulate synchronization ConfigMaps. The ConfigMap-backed Sync Service provider directly performs create, get, update, and delete operations with the server's Kubernetes client without auth.CanI checks. Argo Server in server mode or SSO mode without RBAC is exposed, allowing ConfigMap reads and writes and workflow service interruption.
Summary
What happened
Missing authorization in Argo Workflows 4.0.0 through 4.0.4 allows remote authenticated users to manipulate synchronization ConfigMaps. The ConfigMap-backed Sync Service provider directly performs create, get, update, and delete operations with the server's Kubernetes client without auth.CanI checks. Argo Server in server mode or SSO mode without RBAC is exposed, allowing ConfigMap reads and writes and workflow service interruption.
The record
- CVE
- CVE-2026-42297
- Published
- May 9, 2026
- Updated
- May 9, 2026
- Vendor
- Argo Project
- Product
- Argo Workflows
- Classifications
- CWE-862, CWE-425, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 2026CVE publishedPublication date reported by the CVE source.
- May 9, 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.
- Affected versionversion=>= 4.0.0, < 4.0.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- Upstream Sync ConfigMap provider proof of conceptproof of concept · demonstrated
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