@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.
CVE-2026-7120
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 23, 2026@fastify/static vulnerable to Authorization Bypass via Non-Canonical URL Paths · Advisory · fastify/fastify-static · GitHub
https://github.com/fastify/fastify-static/security/advisories/GHSA-8pvw-jcv7-9cmjSecurity Advisories | OpenJS Foundation CVE Numbering Authority
https://cna.openjsf.org/security-advisories.htmlVendor Advisories for CVE-2026-7120(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 01:01 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:21 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:43 UTCEG score recompute
- 2026-07-23 03:42 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-7120?
When was CVE-2026-7120 disclosed?
Is CVE-2026-7120 actively exploited?
What is the CVSS score of CVE-2026-7120?
How do I remediate CVE-2026-7120?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-7120
Is Your Infrastructure Affected by CVE-2026-7120?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.