CVE-2025-62156 argo-workflows Zip Slip path traversal allows arbitrary file write and container configuration overwrite
Attackers can write arbitrary files outside the extraction directory via malicious archives, potentially overwriting system configs to escalate privileges or persist in the container.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-62156?
CVE-2025-62156 is a high-severity path traversal vulnerability in argoproj argo-workflows, published on 14 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Versions prior to 3.6.12 and versions 3.7.0 through 3.7.2 contain a Zip Slip path traversal vulnerability in artifact extraction. During artifact extraction the unpack/untar logic (workflow/executor/executor.go) uses filepath.Join(dest, filepath.Clean(header.Name)) without validating that header.Name stays within the intended extraction directory. A malicious archive entry can supply a traversal or absolute path that, after cleaning, overrides the destination directory and causes files to be written outside the /work/tmp extraction path and into system directories such as /etc inside the container. The vulnerability enables arbitrary file creation or overwrite in system configuration locations (for example /etc/passwd, /etc/hosts, /etc/crontab), which can lead to privilege escalation or persistence within the affected container. Update to 3.6.12 or 3.7.3 to remediate the issue.
Weakness: CWE-22
Which versions are affected by CVE-2025-62156?
8 open source packages ship an affected version, including github.com/argoproj/argo-workflows/v3, argo-workflows and github.com/argoproj/argo-workflows. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/argoproj/argo-workflows/v3 Go | All versions | 3.6.12, 3.7.3 |
github.com/argoproj/argo-workflows/v3 Go | All versions | 3.6.12 |
github.com/argoproj/argo-workflows/v3 Go | All versions | 3.6.12 |
github.com/argoproj/argo-workflows/v3 Go | From 3.7.0 | 3.7.3 |
github.com/argoproj/argo-workflows/v3 Go | From 3.7.0 | 3.7.3 |
argo-workflows Bitnami | All versions | 3.6.12, 3.7.3 |
2 more packages
github.com/argoproj/argo-workflows Go | All versions | None |
github.com/argoproj/argo-workflows/v2 Go | All versions | None |
Products include Argoproj Argo Workflows.
How do I fix CVE-2025-62156?
Upgrade github.com/argoproj/argo-workflows/v3 to a fixed version for your release line: 3.6.12 or 3.7.3.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2025-62156 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62156 exists.
Other vulnerabilities in argoproj argo-workflows
- CVE-2026-28229 Argo Workflows has unauthorized access to Argo Workflows Template
- CVE-2026-54526 Argo Workflows: Incomplete fix for CVE-2026-31892: ArtifactGC.PodSpecPatch bypass of Strict/Secure templateReferencing
- CVE-2026-31892 WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode
- CVE-2026-42295 Argo Workflows: Exposure of artifact repository credentials
- CVE-2026-42297 Argo Workflows Is Missing Authorization in Sync ConfigMap Provider
Sources
Also known as BIT-argo-workflows-2025-62156, CLEANSTART-2026-LB77513, CLEANSTART-2026-SQ12497, GHSA-p84v-gxvw-73pf, GO-2025-4023, MINI-2656-8mrj-mr5j and 6 more.