Improperly Controlled Modification of Dynamically-Determined Object Attributes Affecting github.com/argoproj/argo-workflows/workflow/util package, versions <4.0.6
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMARGOPROJARGOWORKFLOWSWORKFLOWUTIL-18016334
- published19 Jul 2026
- disclosed16 Jul 2026
- creditfg0x0, 0xVijay, tonghuaroot
Introduced: 16 Jul 2026
CVE-2026-54526 Â (opens in a new tab)How to fix?
Upgrade github.com/argoproj/argo-workflows/workflow/util to version 4.0.6 or higher.
Overview
Affected versions of this package are vulnerable to Improperly Controlled Modification of Dynamically-Determined Object Attributes via the ArtifactGC.PodSpecPatch handling in workflow/util/merge.go. An attacker can override the artifact-GC pod’s spec by submitting a Workflow with spec.artifactGC.podSpecPatch under workflowTemplateRef in Strict or Secure mode, causing the controller to run attacker-chosen pod settings instead of the hardened defaults. That lets the attacker inject an arbitrary strategic merge patch into the artifact-GC pod, including changes such as a different container image, privileged settings, hostNetwork, or hostPath mounts. For users relying on Strict/Secure template referencing, this breaks the intended restriction and can expose the workflow’s service-account token and node resources.