# CVE-2026-7120: @fastify/static vulnerable to Authorization Bypass via Non-Canonical URL Paths

> An attacker can bypass allowedPath restrictions in @fastify/static by using non-canonical URL paths, gaining unauthorized read access to restricted files.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-8pvw-jcv7-9cmj, MINI-mh3f-2r72-757f

## What is CVE-2026-7120?

CVE-2026-7120 is a medium-severity authentication bypass vulnerability in @fastify/static, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize)

## Which versions are affected by CVE-2026-7120?

2 open source packages ship an affected version, including @fastify/static. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@fastify/static` | npm | All versions | 10.1.2 |
| `@fastify/static` | npm | All versions | 10.1.2 |

Products: Fastify Fastify-Static.

## How do I fix CVE-2026-7120?

Upgrade @fastify/static to 10.1.2 or later.

## Is CVE-2026-7120 being exploited?

There is no known exploitation of CVE-2026-7120 in the wild and no public exploit code.

## Other vulnerabilities in @fastify/static

- [CVE-2021-22964](https://insights.sbomify.com/CVE-2021-22964/): DOS and Open Redirect with user input (high 8.8)
- [CVE-2026-18427](https://insights.sbomify.com/CVE-2026-18427/): @fastify/static vulnerable to route guard bypass via non-canonical path segments (high 7.5)
- [CVE-2026-15074](https://insights.sbomify.com/CVE-2026-15074/): @fastify/static vulnerable to route guard bypass via path traversal (high 7.5)
- [CVE-2021-22963](https://insights.sbomify.com/CVE-2021-22963/): URL Redirection to Untrusted Site ('Open Redirect') in fastify-static (medium 6.1)
- [CVE-2026-6414](https://insights.sbomify.com/CVE-2026-6414/): @fastify/static vulnerable to route guard bypass via encoded path separators (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7120 and fix it if it is affected.

What it is: CVE-2026-7120 is a medium-severity authentication bypass vulnerability in @fastify/static, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7120 in the wild and no public exploit code.

Affected packages and fixed versions:
- @fastify/static (npm): affected all versions; fixed in 10.1.2
- @fastify/static (npm): affected all versions; fixed in 10.1.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7120/ (Markdown: https://insights.sbomify.com/CVE-2026-7120/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7120
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7120
- OSV: https://osv.dev/vulnerability/CVE-2026-7120

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7120/
Summaries are generated and may contain mistakes; the official description above is the record.