Argo Workflows Is Missing Authorization in Sync ConfigMap Provider
21Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackcvss 8.5epss 0.5%
probabilidade de exploração
0.5%top 59% das CVEs
exploração observada
nãonenhuma fonte reporta
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:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:H/SA:H
Produtos afetados
argoproj · argo-workflowsReferências
https://access.redhat.com/security/cve/CVE-2026-42297https://bugzilla.redhat.com/show_bug.cgi?id=2468448https://github.com/argoproj/argo-workflows/commit/09fff05e0830c14a5e36cc40597ad84881db1ab6https://github.com/argoproj/argo-workflows/releases/tag/v4.0.5https://github.com/argoproj/argo-workflows/security/advisories/GHSA-xchc-cqwg-g76qhttps://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42297.json