CVE-2025-66626: argoproj argo-workflows · Relative Path Traversal
Affects argoproj argo-workflowsSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 8.1 High : upgrade to 3.7.5 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.7.5
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 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.
What to do
Upgrade argoproj/argo-workflows to 3.7.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubargoproj/argo-workflowspkg:github/argoproj/argo-workflowsOther threats | 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
European organizations should immediately upgrade Argo Workflows to versions 3.6.14 or 3.7.5 or later to remediate this vulnerability. Until upgrades are applied, restrict network access to Argo Workflows endpoints to trusted users and networks to limit exposure. Implement strict validation and sanitization of all archive files used in workflows, particularly scrutinizing symbolic links to prevent path traversal. Employ Kubernetes Pod Security Policies or equivalent admission controllers to restrict execution privileges and prevent unauthorized file overwrites. Monitor workflow execution logs and container file systems for unusual modifications to /var/run/argo/argoexec or other critical files. Use runtime security tools to detect anomalous pod startup behaviors indicative of exploitation. Regularly audit and rotate credentials and secrets used within workflows to limit attacker persistence. Finally, coordinate with cloud providers and security teams to ensure rapid incident response capabilities in case of exploitation.
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.
References
- github.com/argoproj/argo-workflows/security/advisories/GHSA-xrqc-7xgx-c9vh (opens in a new tab)
- github.com/argoproj/argo-workflows/commit/6b92af23f35aed4d4de8b04adcaf19d68f006de1 (opens in a new tab)
- github.com/advisories/GHSA-p84v-gxvw-73pf (opens in a new tab)
- github.com/argoproj/argo-workflows/blob/5291e0b01f94ba864f96f795bb500f2cfc5ad799/workflow/executor/executor.go (opens in a new tab)