CVE-2026-7120
@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.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 5.3
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS probability
- 0.37%
- CWE
- CWE-180
- Published
- 2026-07-23
- Last modified
- 2026-07-24
Affected products
- @fastify/static @fastify/static
- @fastify/static @fastify/static
Weakness type
Related vulnerabilities
- CVE-2026-82736 — Ash.Type.CiString validates length and match constraints before case folding, allowing constraint bypass
- CVE-2026-82481 — The cohttp package before 6.3.0 for OCaml allows directory traversal.
- CVE-2026-76203 — CSS sanitizer bypass in Pentestify report themes allows forced outbound requests
- CVE-2026-73416 — jupyterlab: PyPI extension blocklist package-name canonicalization bypass
- CVE-2026-73420 — NextAuth.js: Email normalizer validates the address before Unicode normalization, allowing a homoglyph @ bypass
- CVE-2026-72917 — AnythingLLM: Password recovery accepts one recovery code twice after whitespace normalization
- CVE-2026-69246 — Guzzle: Noncanonical host can bypass host-based checks
- CVE-2026-69245 — Guzzle: Noncanonical cookie domain keeps subdomain scope