Arbitrary file write via unsanitized archive paths
Published Feb 11, 2026 · Updated Feb 11, 2026
Path traversal in nanotar 0.2.0 and earlier allows remote attackers to write files outside extraction directories via crafted tar archives. parseTar() and parseTarGzip() return entry names from standard and PAX headers without rejecting traversal segments or absolute paths. Exploitation requires a consuming application to write returned entries using those names, enabling overwrite of files writable by that process.
Summary
What happened
Path traversal in nanotar 0.2.0 and earlier allows remote attackers to write files outside extraction directories via crafted tar archives. parseTar() and parseTarGzip() return entry names from standard and PAX headers without rejecting traversal segments or absolute paths. Exploitation requires a consuming application to write returned entries using those names, enabling overwrite of files writable by that process.
The record
- CVE
- CVE-2025-69874
- Published
- Feb 11, 2026
- Updated
- Feb 11, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 2026CVE publishedPublication date reported by the CVE source.
- Feb 11, 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.
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
- nanotar 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