# CVE-2026-42296: Argo has incomplete fix for CVE-2026-31892: hostNetwork, securityContext, serviceAccountName bypass templateReferencing Strict/Secure > Attackers with workflow creation permissions can bypass strict template referencing to gain host network access or modify pod security contexts. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`) - **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-42296, ECHO-81a1-8435-98ad, GHSA-3775-99mw-8rp4, GO-2026-5072, MINI-26gf-8j6m-v682, MINI-2q6g-q42f-xjqm, MINI-3c3x-95w4-pccw, MINI-3fmr-qg8r-73m3, MINI-876r-mph5-89rj, MINI-cvfj-v438-3cm6, MINI-g23r-93c9-3hpr, MINI-mrv8-vwpj-4x77, ROOT-APP-GOBINARY-CVE-2026-42296 ## What is CVE-2026-42296? CVE-2026-42296 is a high-severity 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. Prior to versions 3.7.14 and 4.0.5, a user with create Workflow permission can bypass templateReferencing: Strict to get host network access, switch service accounts, override pod security context, add tolerations to schedule on control-plane nodes, or enable SA token mounting. This defeats the stated purpose of the feature. The practical impact depends on what Kubernetes-level controls are in place. Clusters with PodSecurity admission or OPA/Gatekeeper would independently block some of these (like hostNetwork). Clusters that rely on Argo's Strict mode as the primary enforcement layer are fully exposed. This issue has been patched in versions 3.7.14 and 4.0.5. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-42296? 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.14 | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.7.14 | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.7.14 | | `argo-workflows` | Bitnami | All versions | 3.7.14, 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/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 | Products: Argoproj Argo Workflows. ## How do I fix CVE-2026-42296? Upgrade github.com/argoproj/argo-workflows/v3 to 3.7.14 or later. ## Is CVE-2026-42296 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42296 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-2026-42297](https://insights.sbomify.com/CVE-2026-42297/): Argo Workflows Is Missing Authorization in Sync ConfigMap Provider (high 8.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-42296 and fix it if it is affected. What it is: CVE-2026-42296 is a high-severity 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-42296 exists. Affected packages and fixed versions: - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.7.14 - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.7.14 - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.7.14 - argo-workflows (Bitnami): affected all versions; fixed in 3.7.14, 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/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 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-42296/ (Markdown: https://insights.sbomify.com/CVE-2026-42296/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42296 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42296 - OSV: https://osv.dev/vulnerability/CVE-2026-42296 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-42296/ Summaries are generated and may contain mistakes; the official description above is the record.