Container file overwrite via unchecked archive paths
Published Oct 14, 2025 · Updated Oct 14, 2025
Path traversal in Argo Project Argo Workflows before 3.6.12 and 3.7.0 through 3.7.2 allows remote authenticated users to write files. The untar logic passes a cleaned, attacker-controlled archive entry to filepath.Join without verifying that the result remains under /work/tmp. Workflow-submission privileges are required, and successful exploitation can overwrite container configuration files for persistence or privilege escalation.
Summary
What happened
Path traversal in Argo Project Argo Workflows before 3.6.12 and 3.7.0 through 3.7.2 allows remote authenticated users to write files. The untar logic passes a cleaned, attacker-controlled archive entry to filepath.Join without verifying that the result remains under /work/tmp. Workflow-submission privileges are required, and successful exploitation can overwrite container configuration files for persistence or privilege escalation.
The record
- CVE
- CVE-2025-62156
- Published
- Oct 14, 2025
- Updated
- Oct 14, 2025
- Vendor
- Argo Project
- Product
- Argo Workflows
- Classifications
- CWE-22, CWE-23
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 14, 2025CVE publishedPublication date reported by the CVE source.
- Oct 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.6.12
- Affected versionversion=>= 3.7.0, < 3.7.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-p84v-gxvw-73pf proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo