# CVE-2026-28229: Argo Workflows has unauthorized access to Argo Workflows Template > Attackers can retrieve sensitive WorkflowTemplate content, including secrets, by sending requests with a dummy bearer token due to missing authorization checks. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Mar 2026 - **Updated:** 15 Jul 2026 - **Also known as:** BIT-argo-workflows-2026-28229, ECHO-a921-375a-81f1, GHSA-56px-hm34-xqj5, GO-2026-4678, MINI-6mc8-xg5c-629r, MINI-7x9c-rh86-j8m9, MINI-c7gf-2rcc-927x, MINI-cjwr-h7gv-vrc2, MINI-f4f4-2gvx-3qwc, MINI-f9cm-hvwg-j88f, MINI-fpx4-hxv7-27hg, MINI-x523-9wgw-6m2p, ROOT-APP-GOBINARY-CVE-2026-28229 ## What is CVE-2026-28229? CVE-2026-28229 is a critical missing authorization vulnerability in argoproj argo-workflows, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to 4.0.2 and 3.7.11, Workflow templates endpoints allow any client to retrieve WorkflowTemplates (and ClusterWorkflowTemplates). Any request with a Authorization: Bearer nothing token can leak sensitive template content, including embedded Secret manifests. This vulnerability is fixed in 4.0.2 and 3.7.11. Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-28229? 9 open source packages ship an affected version, including github.com/argoproj/argo-workflows/v3, argo-workflows and github.com/argoproj/argo-workflows. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.7.11 | | `github.com/argoproj/argo-workflows/v3` | Go | From 3.7.0 | 3.7.11 | | `github.com/argoproj/argo-workflows/v3` | Go | From 3.7.0 | 3.7.11 | | `argo-workflows` | Bitnami | All versions | 3.7.11, 4.0.2 | | `github.com/argoproj/argo-workflows` | Go | All versions | None | | `github.com/argoproj/argo-workflows/v2` | Go | All versions | None | | `github.com/argoproj/argo-workflows/v4` | Go | All versions | 4.0.2 | | `github.com/argoproj/argo-workflows/v4` | Go | All versions | 4.0.2 | | `github.com/argoproj/argo-workflows/v4` | Go | All versions | 4.0.2 | Products: Argoproj Argo Workflows. ## How do I fix CVE-2026-28229? Upgrade github.com/argoproj/argo-workflows/v3 to 3.7.11 or later. ## Is CVE-2026-28229 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28229 exists. ## Other vulnerabilities in argoproj argo-workflows - [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-2026-42297](https://insights.sbomify.com/CVE-2026-42297/): Argo Workflows Is Missing Authorization in Sync ConfigMap Provider (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-28229 and fix it if it is affected. What it is: CVE-2026-28229 is a critical missing authorization vulnerability in argoproj argo-workflows, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28229 exists. Affected packages and fixed versions: - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.7.11 - github.com/argoproj/argo-workflows/v3 (Go): affected from 3.7.0; fixed in 3.7.11 - github.com/argoproj/argo-workflows/v3 (Go): affected from 3.7.0; fixed in 3.7.11 - argo-workflows (Bitnami): affected all versions; fixed in 3.7.11, 4.0.2 - 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/v4 (Go): affected all versions; fixed in 4.0.2 - github.com/argoproj/argo-workflows/v4 (Go): affected all versions; fixed in 4.0.2 - github.com/argoproj/argo-workflows/v4 (Go): affected all versions; fixed in 4.0.2 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-28229/ (Markdown: https://insights.sbomify.com/CVE-2026-28229/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-28229 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-28229 - OSV: https://osv.dev/vulnerability/CVE-2026-28229 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-28229/ Summaries are generated and may contain mistakes; the official description above is the record.