CVE-2026-7120

@fastify/static vulnerable to Authorization Bypass via Non-Canonical URL Paths

MEDIUM
5.3
CVSS Score
Published: July 23, 2026 at 02:48 AM UTC
Updated: July 28, 2026 at 05:15 PM UTC
2 products affected across 2 vendorsFastify Static@fastify/static

Using @fastify/static by @fastify/static?

Get instant alerts when new vulnerabilities affect @fastify/static - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

@fastify/static evaluates the allowedPath callback before normalizing dot segments and duplicate path separators in the pathname used for file resolution. Versions up to and including 10.1.1 are affected. An unauthenticated attacker can bypass allowedPath restrictions by requesting equivalent non-canonical pathnames, causing files that were intended to be denied to be served anyway. The bypass does not allow access outside the configured static root by itself, it defeats path-based filtering only. The issue is patched in @fastify/static 10.1.2.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.1.2
Affected range stops below 10.1.2, so it looks safe — our inference, not a vendor statement
v < 10.1.2
Vendor states this is fixed in 10.1.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUMopenjs
Vector?

Quick Info

StatusANALYZED
CWE
CWE-180

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card