# CVE-2026-42297: Argo Workflows Is Missing Authorization in Sync ConfigMap Provider > Authenticated users can bypass authorization to create, read, update, or delete Kubernetes ConfigMaps in Argo Workflows. - **Severity:** High 8.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`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 May 2026 - **Updated:** 15 Jul 2026 - **Also known as:** BIT-argo-workflows-2026-42297, GHSA-xchc-cqwg-g76q, GO-2026-5751, MINI-38h2-2289-xq7x, MINI-4526-5rf6-q3hm, MINI-5mpm-qhqg-84hg, MINI-85g5-w3hr-677g, MINI-cqgh-jrwp-rr97, MINI-gqmp-pp4q-ph9x, MINI-j952-cmvg-jx8r, MINI-q7gr-rh85-hh8g, MINI-vm5c-p9q4-5m8r, MINI-vpp2-rj25-mhph, MINI-x625-8776-3hpv, MINI-x829-4h7x-jw89 ## What is CVE-2026-42297? CVE-2026-42297 is a high-severity missing authorization vulnerability in argoproj argo-workflows, published on 9 May 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-425 (Direct Request), CWE-862 (Missing Authorization) ## Which versions are affected by CVE-2026-42297? 7 open source packages ship an affected version, including github.com/argoproj/argo-workflows/v4, argo-workflows and github.com/argoproj/argo-workflows. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-workflows/v4` | Go | From 4.0.0 | 4.0.5 | | `github.com/argoproj/argo-workflows/v4` | Go | From 4.0.0 | 4.0.5 | | `github.com/argoproj/argo-workflows/v4` | Go | From 4.0.0 | 4.0.5 | | `argo-workflows` | Bitnami | From 4.0.0 | 4.0.5 | | `github.com/argoproj/argo-workflows` | Go | All versions | None | | `github.com/argoproj/argo-workflows/v2` | Go | All versions | None | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | None | Products: Argoproj Argo Workflows. ## How do I fix CVE-2026-42297? Upgrade github.com/argoproj/argo-workflows/v4 to 4.0.5 or later. ## Is CVE-2026-42297 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42297 exists. ## Other vulnerabilities in argoproj argo-workflows - [CVE-2026-28229](https://insights.sbomify.com/CVE-2026-28229/): Argo Workflows has unauthorized access to Argo Workflows Template (critical 9.8) - [CVE-2026-54526](https://insights.sbomify.com/CVE-2026-54526/): Argo Workflows: Incomplete fix for CVE-2026-31892: ArtifactGC.PodSpecPatch bypass of Strict/Secure templateReferencing (high 8.9) - [CVE-2026-31892](https://insights.sbomify.com/CVE-2026-31892/): WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode (high 8.9) - [CVE-2026-42295](https://insights.sbomify.com/CVE-2026-42295/): Argo Workflows: Exposure of artifact repository credentials (high 8.5) - [CVE-2025-62157](https://insights.sbomify.com/CVE-2025-62157/): Argo Workflows exposes artifact repository credentials in workflow-controller logs (high 8.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-42297 and fix it if it is affected. What it is: CVE-2026-42297 is a high-severity missing authorization vulnerability in argoproj argo-workflows, published on 9 May 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42297 exists. Affected packages and fixed versions: - github.com/argoproj/argo-workflows/v4 (Go): affected from 4.0.0; fixed in 4.0.5 - github.com/argoproj/argo-workflows/v4 (Go): affected from 4.0.0; fixed in 4.0.5 - github.com/argoproj/argo-workflows/v4 (Go): affected from 4.0.0; fixed in 4.0.5 - argo-workflows (Bitnami): affected from 4.0.0; fixed in 4.0.5 - github.com/argoproj/argo-workflows (Go): affected all versions; no fix listed - github.com/argoproj/argo-workflows/v2 (Go): affected all versions; no fix listed - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-42297/ (Markdown: https://insights.sbomify.com/CVE-2026-42297/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42297 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42297 - OSV: https://osv.dev/vulnerability/CVE-2026-42297 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-42297/ Summaries are generated and may contain mistakes; the official description above is the record.