# CVE-2026-31892: WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode > Attackers can bypass strict template security controls in Argo Workflows by injecting podSpecPatch, allowing unauthorized pod configuration changes. - **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/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:** 11 Mar 2026 - **Updated:** 15 Jul 2026 - **Also known as:** BIT-argo-workflows-2026-31892, ECHO-11ce-20c3-b91e, GHSA-3wf5-g532-rcrr, GO-2026-4681, MINI-4g5j-fgcr-vv5p, MINI-7fmc-rh5x-78p7, MINI-fmmh-3x65-6647, MINI-gx4c-c57m-fmpm, MINI-phw7-m59j-f8j5, MINI-rq9f-v6hh-m4w8, MINI-vqm7-qfg3-26h5, MINI-wph3-9354-ccq3, ROOT-APP-GOBINARY-CVE-2026-31892 ## What is CVE-2026-31892? CVE-2026-31892 is a high-severity vulnerability in argoproj argo-workflows, published on 11 Mar 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 2.9.0 to before 4.0.2 and 3.7.11, A user who can submit Workflows can completely bypass all security settings defined in a WorkflowTemplate by including a podSpecPatch field in their Workflow submission. This works even when the controller is configured with templateReferencing: Strict, which is specifically documented as a mechanism to restrict users to admin-approved templates. The podSpecPatch field on a submitted Workflow takes precedence over the referenced WorkflowTemplate during spec merging and is applied directly to the pod spec at creation time with no security validation. This vulnerability is fixed in 4.0.2 and 3.7.11. Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision), CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-31892? 11 open source packages ship an affected version, including github.com/argoproj/argo-workflows, argo-workflows and github.com/argoproj/argo-workflows/v2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-workflows` | Go | All versions | None | | `github.com/argoproj/argo-workflows` | Go | From 2.9.0 | None | | `github.com/argoproj/argo-workflows` | Go | From 2.9.0 | None | | `argo-workflows` | Bitnami | All versions | 3.7.11, 4.0.2 | | `github.com/argoproj/argo-workflows/v2` | Go | From 2.9.0 | None | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.7.11 | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.7.11 | | `github.com/argoproj/argo-workflows/v3` | Go | All versions | 3.7.11 | | `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-31892? Upgrade to a fixed version. ## Is CVE-2026-31892 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-31892 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-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-31892 and fix it if it is affected. What it is: CVE-2026-31892 is a high-severity vulnerability in argoproj argo-workflows, published on 11 Mar 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-31892 exists. Affected packages and fixed versions: - github.com/argoproj/argo-workflows (Go): affected all versions; no fix listed - github.com/argoproj/argo-workflows (Go): affected from 2.9.0; no fix listed - github.com/argoproj/argo-workflows (Go): affected from 2.9.0; no fix listed - argo-workflows (Bitnami): affected all versions; fixed in 3.7.11, 4.0.2 - github.com/argoproj/argo-workflows/v2 (Go): affected from 2.9.0; no fix listed - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.7.11 - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.7.11 - github.com/argoproj/argo-workflows/v3 (Go): affected all versions; fixed in 3.7.11 - 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-31892/ (Markdown: https://insights.sbomify.com/CVE-2026-31892/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31892 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31892 - OSV: https://osv.dev/vulnerability/CVE-2026-31892 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-31892/ Summaries are generated and may contain mistakes; the official description above is the record.