High severity · published Jul 23, 2026
CVE-2026-15074
@fastify/static vulnerable to route guard bypass via path traversal
7.5
CVSS
0.7%
EPSS
No
On KEV
Description
@fastify/static up to and including version 10.1.0 fails to reject dot-dot path segments in request pathnames before the file-resolution stage. This is a bypass of the earlier fix for CVE-2026-6414, which only covered encoded forward slashes. Because the underlying send library normalizes dot segments before applying its own path-traversal guard, an unauthenticated attacker can bypass any route-scoped middleware and read files inside the static root that live under the guarded URL prefix. The bypass does not allow access outside the configured static root by itself, it defeats route-guard filtering only. The issue is patched in @fastify/static 10.1.1.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.7% · higher than 52% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
FA
@fastify/static · @fastify/static
before 10.1.1 · source: vendor
FA
Fastify-static · Fastify
before 10.1.1 · source: NVD
Affected product
FA
@fastify/static
@fastify/static
More from @fastify/static
7.5
CVE-2026-18427
@fastify/static vulnerable to route guard bypass via non-canonical path segments
5.9
CVE-2026-6414
@fastify/static vulnerable to route guard bypass via encoded path separators
5.3
CVE-2026-90982
@fastify/static vulnerable to route guard bypass via path case-folding
5.3
CVE-2026-7120
@fastify/static vulnerable to Authorization Bypass via Non-Canonical URL Paths
5.3
CVE-2026-6410
@fastify/static vulnerable to path traversal in directory listing