CVE-2026-42297
Argoproj Argo Workflows broken access control
- Published9 May 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/security/cve/CVE-2026-42297
- https://bugzilla.redhat.com/show_bug.cgi?id=2468448
- https://github.com/argoproj/argo-workflows/commit/09fff05e0830c14a5e36cc40597ad84881db1ab6
- https://github.com/argoproj/argo-workflows/releases/tag/v4.0.5
- https://github.com/argoproj/argo-workflows/security/advisories/GHSA-xchc-cqwg-g76q
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42297.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-42297 being actively exploited?
CVE-2026-42297 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.53%.
How severe is CVE-2026-42297?
CVE-2026-42297 has a CVSS 3.1 base score of 8.3, rated high. EPSS estimates a 0.53% probability of exploitation.
Which products are affected by CVE-2026-42297?
Affected products include Argoproj Argo Workflows.
How do I fix CVE-2026-42297?
Upgrade affected software to a fixed version, for example Argoproj Argo Workflows 4.0.5 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-42297 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.