CVE-2025-62156: V3 · Argo Workflow has a Zipslip Vulnerability
Affects github.com/argoproj/argo-workflows/v3Source GCVE Database
Not known to be exploited · CVSS 8.1 High : upgrade to 3.6.12 soon.
Data as of 4 Nov 2026, 18:23 UTC
- Patch
- Available – fixed in 3.6.12, 3.7.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Upgrade github.com/argoproj/argo-workflows/v3 to 3.6.12; github.com/argoproj/argo-workflows/v3 to 3.7.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/argoproj/argo-workflows/v3 | Affected
| Fixed in
|
| Gogithub.com/argoproj/argo-workflows/v3 | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in Argo Workflows versions 3.6.12 and 3.7.3 that fixes this Zip Slip vulnerability by properly validating paths during artifact extraction. Users should upgrade to these fixed versions or later. Until patched, avoid extracting untrusted archives in workflows or restrict artifact sources to trusted origins. No vendor advisory indicates that no action is required or that the issue is already mitigated, so upgrading is the recommended remediation.
Description
A Zip Slip vulnerability (CVE-2025-62156) exists in Argo Workflows versions prior to 3.6.12 and between 3.7.0 and before 3.7.3. The flaw occurs during artifact extraction where path traversal entries in tar.gz archives allow files to be written outside the intended extraction directory, specifically into system directories like /etc/. This enables attackers to overwrite critical configuration files within container environments. The vulnerability arises from improper path validation in the untar() function, which uses filepath.Join with cleaned but unchecked paths, allowing absolute paths to escape the extraction directory. A proof of concept demonstrates exploitation by uploading a crafted archive and mounting volumes to achieve file creation in /etc/.
References
- github.com/argoproj/argo-workflows/security/advisories/GHSA-p84v-gxvw-73pf (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2025-62156 (opens in a new tab)
- github.com/argoproj/argo-workflows/commit/5659ad9b641fcf52c04ed594cd6493f9170f6011 (opens in a new tab)
- github.com/argoproj/argo-workflows/commit/9f6bc5d236cd1b24d607943384511d71ad17a4c3 (opens in a new tab)
- github.com/argoproj/argo-workflows (opens in a new tab)
- github.com/argoproj/argo-workflows/blob/946a2d6b9ac3309371fe47f49ae94c33ca7d488d/workflow/executor/executor.go (opens in a new tab)
- pkg.go.dev/vuln/GO-2025-4023 (opens in a new tab)