Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
8.6

Argo Workflows pre‑3.7.15 permits unsafe pod modifications

published 8 days ago
Summary

Versions of Argo Workflows before 3.7.15 and 4.0.6 let a user add malicious settings—such as privileged containers, host‑path volumes, or custom commands—to the pod that cleans up artifacts. This can bypass the security checks meant to keep workflow templates safe. Upgrade to version 3.7.15 or later (or 4.0.6 or later) to stop the issue.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
Ecosystem VendorProductAffected versions
Docker Hardened Images:Alpine:3.23 docker hardened images argo-workflows-3-dev All versions
Docker Hardened Images:Alpine:3.23 docker hardened images argo-workflows-3-fips-dev All versions
Docker Hardened Images:Alpine:3.23 docker hardened images argo-workflows-3-fips All versions
Docker Hardened Images:Alpine:3.23 docker hardened images argo-workflows-3 All versions
Docker Hardened Images:Alpine:3.23 docker hardened images argo-workflows-4-dev All versions
Docker Hardened Images:Alpine:3.23 docker hardened images argo-workflows-4-fips-dev All versions
Docker Hardened Images:Alpine:3.23 docker hardened images argo-workflows-4-fips All versions
Docker Hardened Images:Alpine:3.23 docker hardened images argo-workflows-4 All versions
Original advisory text
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior…
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.
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit (estimated)
  • Gives an attacker full control (estimated)
Severity
8.6 High
Timeline
Published13 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
Track software like this
Free during beta