Skip to main content
VulnerabilityPublished

CVE-2025-62156: argoproj argo-workflows · Path Traversal

Affects argoproj argo-workflowsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 3.6.12 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.6.12
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Upgrade argoproj argo-workflows to 3.6.12.

Affected software

ProductAffectedFixed in
argoproj argo-workflowsAffected
  • <3.6.12
Fixed in
  • 3.6.12

AI-suggested

European organizations should immediately assess their use of Argo Workflows and identify deployments running affected versions (<3.6.12 and 3.7.0 to 3.7.2). The primary mitigation is to upgrade to Argo Workflows version 3.6.12 or 3.7.3, where the vulnerability is patched. Until upgrades can be applied, organizations should restrict access to artifact sources and ensure that only trusted archives are processed. Implement runtime security controls to monitor and alert on unexpected file writes within containers, especially to sensitive paths like /etc. Employ container security best practices such as running containers with least privilege, using read-only root filesystems where feasible, and applying Kubernetes Pod Security Policies or OPA Gatekeeper policies to limit container capabilities. Regularly audit container images and workflows for suspicious artifacts. Network segmentation and zero-trust principles can limit the blast radius if a container is compromised. Finally, integrate vulnerability scanning and continuous monitoring in CI/CD pipelines to detect and prevent deployment of vulnerable versions.

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.

References

Community reviews

Loading reviews…