Unauthenticated file disclosure via encoded path separators
Published Apr 16, 2026 · Updated Apr 16, 2026
URL-encoding mishandling in Fastify @fastify/static 8.0.0 through 9.1.0 allows remote attackers to read guarded static files. The plugin decodes %2F before filesystem resolution while the router treats it literally, so an encoded separator evades the matching route guard. Exposure requires an application to rely on route-based middleware or guards to restrict files inside the configured static root.
Summary
What happened
URL-encoding mishandling in Fastify @fastify/static 8.0.0 through 9.1.0 allows remote attackers to read guarded static files. The plugin decodes %2F before filesystem resolution while the router treats it literally, so an encoded separator evades the matching route guard. Exposure requires an application to rely on route-based middleware or guards to restrict files inside the configured static root.
The record
- CVE
- CVE-2026-6414
- Published
- Apr 16, 2026
- Updated
- Apr 16, 2026
- Vendor
- Fastify
- Product
- @fastify/static
- Classifications
- CWE-177, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2026CVE publishedPublication date reported by the CVE source.
- Apr 16, 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=8.0.0 <9.1.1
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
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