Arbitrary file write via archive separator rewrite
Published Jul 15, 2026 · Updated Jul 15, 2026
Path traversal in File Browser 2.63.6 through 2.63.16 allows remote authenticated users to write files outside an extraction directory. The archive builder in http/raw.go replaces every backslash in NameInArchive with a slash and passes the result to the archiver without rejecting parent-directory segments. Create permission is enough to plant the filename, but another user must download and extract the archive with an extractor that honors traversal entries.
Summary
What happened
Path traversal in File Browser 2.63.6 through 2.63.16 allows remote authenticated users to write files outside an extraction directory. The archive builder in http/raw.go replaces every backslash in NameInArchive with a slash and passes the result to the archiver without rejecting parent-directory segments. Create permission is enough to plant the filename, but another user must download and extract the archive with an extractor that honors traversal entries.
The record
- CVE
- CVE-2026-62843
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- File Browser Contributors
- Product
- File Browser
- Classifications
- CWE-22, CWE-23, T1204.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.63.6, < 2.63.17
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
- Upstream authenticated archive traversal PoCproof 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