Arbitrary file writes via unsanitized archive paths
Published Jun 15, 2026 · Updated Jun 15, 2026
Path traversal in OCaml-tar before 3.5.0 allows attackers to write files outside the extraction directory via a crafted archive. Tar_unix.extract passes the archive-controlled header filename through Filename.concat and then to Unix.openfile without sanitizing parent-directory segments. An application must extract an attacker-supplied archive; resulting writes use the extracting process's filesystem permissions.
Summary
What happened
Path traversal in OCaml-tar before 3.5.0 allows attackers to write files outside the extraction directory via a crafted archive. Tar_unix.extract passes the archive-controlled header filename through Filename.concat and then to Unix.openfile without sanitizing parent-directory segments. An application must extract an attacker-supplied archive; resulting writes use the extracting process's filesystem permissions.
The record
- CVE
- CVE-2026-45390
- Published
- Jun 15, 2026
- Updated
- Jun 15, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, CWE-61, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2026CVE publishedPublication date reported by the CVE source.
- Jun 15, 2026Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- OCaml-tar path traversal 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