Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-54526: 0.55% estimated exploitation activity in the next 30 days; percentile 46.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The allow-list fix for CVE-2026-31892 (GHSA-3wf5-g532-rcrr), and its follow-up coverage of hostNetwork/securityContext/serviceAccountName in GHSA-3775-99mw-8rp4, is incomplete. workflow/util/merge.go ValidateUserOverrides / SanitizeUserWorkflowSpec walk only the top-level fields of WorkflowSpec via reflection. WorkflowSpec.ArtifactGC is allow-listed because admins want users to configure artifact garbage collection. 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. A user submitting a Workflow under templateReferencing: Strict or Secure can therefore still inject an arbitrary strategic merge patch into the artifact-GC pod (hostPath volumes, privileged: true, arbitrary image and command, hostNetwork: true), defeating the stated purpose of Strict/Secure reference mode. Details Locations in main…

Published by the source

13 Aug 2026, 14:16 UTC

Last modified by the source

21 Sep 2026, 02:47 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-48p8-g2fx-3wwm

2. Revision 3 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6223

4. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-48p8-g2fx-3wwm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54526

Advisory: Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892)
IDs: CVE-2026-54526, GHSA-48p8-g2fx-3wwm
Record: https://patchnext.com/advisories/cve-2026-54526 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/argoproj/argo-workflows/v4 4.0.6; github.com/argoproj/argo-workflows/v3 3.7.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-workflows/v4: affected >= 4.0.0, < 4.0.6; fixed in 4.0.6
- Go github.com/argoproj/argo-workflows/v3: affected < 3.7.15; fixed in 3.7.15
- Go github.com/argoproj/argo-workflows/v2: affected every version
- Go github.com/argoproj/argo-workflows: affected <= 2.5.3-rc4

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-workflows/v4: check the installed version with your package manager.
- Go github.com/argoproj/argo-workflows/v3: check the installed version with your package manager.
- Go github.com/argoproj/argo-workflows/v2: check the installed version with your package manager.
- Go github.com/argoproj/argo-workflows: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-workflows/v4, github.com/argoproj/argo-workflows/v3, github.com/argoproj/argo-workflows/v2, github.com/argoproj/argo-workflows.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-48p8-g2fx-3wwm (OSV record GHSA-48p8-g2fx-3wwm lists affected ranges: Go github.com/argoproj/argo-workflows/v4 >=4.0.0 =0 =0 <=2.5.3-rc4)
- Verified: https://osv.dev/vulnerability/GO-2026-6223 (OSV record GO-2026-6223 lists affected ranges: Go github.com/argoproj/argo-workflows >=0; Go github.com/argoproj/argo-workflows/v2 >=0; Go github.com/argoproj/argo-workflows/v3 >=0 =4.0.0 <4.0.6 (fixed))
- Verified: https://github.com/advisories/GHSA-48p8-g2fx-3wwm (GitHub-reviewed advisory GHSA-48p8-g2fx-3wwm lists affected ranges: Go github.com/argoproj/argo-workflows/v4 >=4.0.0 =0 =0 <=2.5.3-rc4)

Commands are suggestions: review each one before running it.