Arbitrary file overwrite via trailing path component
Published Feb 11, 2026 · Updated Feb 11, 2026
Path traversal in BusyBox 1.36.1 and 1.37.0 allows attackers to overwrite files by extracting a crafted archive. The strip_unsafe_prefix() function fails to reject a trailing .. path component, so archive utilities resolve writes outside the intended directory. Exploitation requires a crafted archive to be extracted while the working directory matches the target; overwritten sensitive files enable code execution.
Summary
What happened
Path traversal in BusyBox 1.36.1 and 1.37.0 allows attackers to overwrite files by extracting a crafted archive. The strip_unsafe_prefix() function fails to reject a trailing .. path component, so archive utilities resolve writes outside the intended directory. Exploitation requires a crafted archive to be extracted while the working directory matches the target; overwritten sensitive files enable code execution.
The record
- CVE
- CVE-2026-26157
- Published
- Feb 11, 2026
- Updated
- Feb 11, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-73, T1204.002
- Attack vector
- local
- 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.
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.
Public exploit references
No public exploit references are available in this record.
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