Fastify published its advisory on 20 November 2026 and identifies every release before 4.0.10 as affected. The issue matters when an application relies on path-scoped Express middleware to protect a route.Fastify rates the vulnerability Critical, with a CVSS 3.1 score of 9.1. The vendor says a remote unauthenticated request can reach a route handler while authentication, authorization, or rate-limiting middleware is skipped. The outcome depends on the handler and the protection that the application placed in middleware.
What it allows
How Does CVE-2026-133120 Bypass Authentication?
Fastify's router can dispatch a route using a path that differs from the URL passed to Express middleware. Express then checks its path-scoped mount against a different interpretation of the request. The handler can run even though the middleware intended to guard that path did not run.
The advisory describes decoding and path-normalization differences as the root cause. In releases since 4.0.3, decoding can change how middleware sees path parameters and query values. A separate request-target mismatch affects earlier releases as well, so the vendor marks all versions before 4.0.10 as vulnerable.
Our defensive reading is to review where authorization actually runs, rather than assuming a route declaration proves protection. The Vulnerability Intelligence platform is the relevant product context for prioritizing affected deployments. For a separate issue in the same plugin, see the Fastify Express middleware bypass profile.
What Does the Exploitation Record Show?
CISA's KEV catalog version 2026.11.20 does not list CVE-2026-133120. That dated catalog status does not determine whether exploitation has occurred. The vendor's network attack description and high confidentiality and integrity impacts support prompt review of reachable applications.
Who is affected
Which @fastify/express Versions Are Affected?
Fastify lists @fastify/express versions before 4.0.10 as affected and 4.0.10 as patched. The decoding-related variants begin with 4.0.3, while the separate request-target mismatch applies to earlier releases too. The advisory does not provide a lower version bound suitable for an automated range check.
Exposure requires an application that uses path-scoped Express middleware to protect a Fastify route. Review authentication, authorization, and rate limits enforced through these mounts, including parameterized, prefixed, regular-expression, and static paths. Check the installed dependency and the version loaded by each running deployment.
How Should Teams Fix and Verify CVE-2026-133120?
Upgrade @fastify/express to 4.0.10 or later, then confirm the running process loads the patched version. Recheck protected routes with authorized and unauthenticated requests, confirming that the middleware runs before any sensitive handler. Record the version and access-control result in the patch management process.
If immediate upgrading is unavailable, Fastify recommends enforcing authentication in a Fastify hook after route resolution. Base that decision on the matched route, then test it against the application's protected paths. Treat this as a temporary control while deploying the vendor fix.
Timeline
-
2026-11-20
Fastify published GHSA-w877-hjcp-88rc and identified @fastify/express 4.0.10 as the patched release.
-
2026-11-21
NVD published the CVE-2026-133120 record and listed a CVSS 3.1 score of 9.1.
What to do
-
Inventory affected deployments
Find running applications with @fastify/express before 4.0.10 and identify path-scoped Express middleware that enforces access controls.
-
Apply the vendor patch
Upgrade @fastify/express to 4.0.10 or later, prioritizing reachable applications whose protected routes depend on scoped middleware.
-
Verify the running fix
Confirm the deployed process loads 4.0.10 or later. Test authorized and unauthenticated access to protected routes and confirm the middleware executes.
-
Use a temporary control if needed
Fastify recommends authentication in a hook after routing, based on the matched route. Validate that control before relying on it.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-133120 in Brandefense Atlas
The Atlas record of CVE-2026-133120: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What causes CVE-2026-133120?
Fastify's router and path-scoped Express middleware can interpret a request path differently. The handler can run while the middleware intended to protect it is skipped.
Which @fastify/express versions need the fix?
Fastify lists all versions before 4.0.10 as affected and 4.0.10 as patched. Check the version loaded by each running deployment.
Is every Fastify application exposed?
The issue concerns applications that rely on path-scoped Express middleware to protect Fastify routes. Impact depends on the protected handler and its application logic.
What is the vendor's temporary workaround?
Fastify recommends enforcing authentication in a Fastify hook after routing, using the matched route for the decision. Deploy 4.0.10 or later for the fix.