Argo Workflows Is Missing Authorization in Sync ConfigMap Provider
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-42297US | high8.3OT elevated | — | ||
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 Conf… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/CVE-2026-42297WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2468448WEB
- https://github.com/argoproj/argo-workflows/commit/09fff05e0830c14a5e36cc40597ad84881db1ab6FIX
- https://github.com/argoproj/argo-workflows/releases/tag/v4.0.5ARTICLE
- https://github.com/argoproj/argo-workflows/security/advisories/GHSA-xchc-cqwg-g76qADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2026-42297WEB
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42297.jsonWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan