Out-of-scope file creation via dangling symlink
Published Jul 8, 2026 · Updated Jul 8, 2026
Path traversal in File Browser before 2.63.16 allows remote authenticated users to create files outside their assigned scope. ScopedFs.within validates the in-scope parent of a dangling symlink after EvalSymlinks returns not-exist, then OpenFile follows that symlink and creates an out-of-scope file. Exploitation requires Create and Modify permissions plus a dangling symlink inside the assigned scope, and it can write only new paths accessible to the service process.
Summary
What happened
Path traversal in File Browser before 2.63.16 allows remote authenticated users to create files outside their assigned scope. ScopedFs.within validates the in-scope parent of a dangling symlink after EvalSymlinks returns not-exist, then OpenFile follows that symlink and creates an out-of-scope file. Exploitation requires Create and Modify permissions plus a dangling symlink inside the assigned scope, and it can write only new paths accessible to the service process.
The record
- CVE
- CVE-2026-55668
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- File Browser Contributors
- Product
- File Browser
- Classifications
- CWE-59, CWE-22
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 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.16
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-8wc8-hf36-mjh9 dangling-symlink 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