CVE-2025-66626 argoproj/argo-workflows is vulnerable to RCE via ZipSlip and symbolic links
Attackers can exploit unsafe archive extraction to overwrite executable files, leading to remote code execution in Argo Workflows pods.
- 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-66626?
CVE-2025-66626 is a high-severity path traversal vulnerability in argoproj argo-workflows, published on 9 Dec 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 3.6.13 and below and versions 3.7.0 through 3.7.4, contain unsafe untar code that handles symbolic links in archives. Concretely, the computation of a link's target and the subsequent check are flawed. An attacker can overwrite the file /var/run/argo/argoexec with a script of their choice, which would be executed at the pod's start. The patch deployed against CVE-2025-62156 is ineffective against malicious archives containing symbolic links. This issue is fixed in versions 3.6.14 and 3.7.5.
Which versions are affected by CVE-2025-66626?
10 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.14, 3.7.5 |
github.com/argoproj/argo-workflows/v3 Go | All versions | 3.6.14 |
github.com/argoproj/argo-workflows/v3 Go | All versions | 3.6.14 |
github.com/argoproj/argo-workflows/v3 Go | From 3.7.0 | 3.7.5 |
github.com/argoproj/argo-workflows/v3 Go | From 3.7.0 | 3.7.5 |
argo-workflows Bitnami | All versions | 2.5.3, 3.6.14 |
4 more packages
github.com/argoproj/argo-workflows Go | All versions | None |
github.com/argoproj/argo-workflows Go | All versions to 2.5.3-rc4 | None |
github.com/argoproj/argo-workflows Go | All versions to 2.5.3-rc4 | None |
github.com/argoproj/argo-workflows/v2 Go | All versions | None |
Products include Argoproj Argo Workflows.
How do I fix CVE-2025-66626?
Upgrade github.com/argoproj/argo-workflows/v3 to a fixed version for your release line: 3.6.14 or 3.7.5.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2025-66626 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66626 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-66626, GHSA-xrqc-7xgx-c9vh, GO-2025-4223, MINI-5jcp-h4cf-4mg3, MINI-5jfh-cwcj-3x5f, MINI-7wxq-mg5r-8pm6 and 4 more.