argoproj argo-workflows up to 3.7.14/4.0.5 ArtifactGC workflow/util/merge.go ValidateUserOverrides/SanitizeUserWorkflowSpec PodSpecPatch injection

Summaryinfo

A vulnerability, which was classified as very critical, has been found in argoproj argo-workflows up to 3.7.14/4.0.5. This issue affects the function ValidateUserOverrides/SanitizeUserWorkflowSpec of the file workflow/util/merge.go of the component ArtifactGC. The manipulation of the argument PodSpecPatch leads to injection. This vulnerability is referenced as CVE-2026-54526. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in argoproj argo-workflows up to 3.7.14/4.0.5 and classified as very critical. This issue affects the function ValidateUserOverrides/SanitizeUserWorkflowSpec of the file workflow/util/merge.go of the component ArtifactGC. The manipulation of the argument PodSpecPatch with an unknown input leads to a injection vulnerability. Using CWE to declare the problem leads to CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-54526 since 06/15/2026. The exploitation is known to be easy. The attack may be initiated remotely. The exploitation requires an enhanced level of successful authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/16/2026). MITRE ATT&CK project uses the attack technique T1055 for this issue.

Upgrading to version 3.7.15 or 4.0.6 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• argoproj

Name

• argo-workflows

Version

• 3.7.0
• 3.7.1
• 3.7.2
• 3.7.3
• 3.7.4
• 3.7.5
• 3.7.6
• 3.7.7
• 3.7.8
• 3.7.9
• 3.7.10
• 3.7.11
• 3.7.12
• 3.7.13
• 3.7.14
• 4.0.0
• 4.0.1
• 4.0.2
• 4.0.3
• 4.0.4
• 4.0.5

Website

• Product: https://github.com/argoproj/argo-workflows/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion