Skip to main content
Menu
CVEs

Fastify Express authentication bypass in RegExp middleware mounts

Only affects @fastify/express 4.0.7 through 4.0.9 with plugins registered under parameterized prefixes that mount RegExp-path middleware. Fixed in 4.0.10.

CVE-2026-133867Published November 21, 2026, updated

9.1CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 4.0.10
Who is exposed
Default setups

Summary

Affected software: @fastify/express, the compatibility layer that runs Express middleware inside Fastify. When middleware is mounted with a regular expression inside a plugin registered under a parameterized prefix, Express skips that middleware while Fastify still runs the route handler, so an unauthenticated attacker can reach protected routes remotely over the network without logging in.

Written by a model

Original description

@fastify/express is a compatibility layer that lets Express middleware run inside the Fastify web framework. In versions 4.0.7 through 4.0.9, the plugin does not rewrite regular-expression mount paths to account for a parameterized plugin prefix, so when middleware is mounted with a regular expression inside a plugin registered under a parameterized prefix, the Express matcher treats the prefix parameter as literal text and never matches the real request path. As a result, Express silently skips that middleware while Fastify still runs the route handler, so an application that relies on regular-expression mounted middleware for authentication or authorization inside a parameterized-prefix plugin exposes protected routes to unauthenticated clients. No special configuration is required beyond a parameterized prefix and a regular-expression mount. The issue is fixed in @fastify/express 4.0.10, and users should upgrade to 4.0.10 or later.

Who should check

Teams running @fastify/express 4.0.7 to 4.0.9 that register plugins under parameterized prefixes such as /tenant/:tenantId and mount auth middleware with RegExp paths.

“>= 4.0.7, < 4.0.10”

github.com

What to do

  1. Check every install: default setups are affected.

  2. Upgrade to a fixed version: 4.0.10.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133867 (@fastify/express vulnerable to middleware bypass via RegExp mount paths under parameterized prefixes), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133867 (entry last updated 2026-11-21):
Affected:
- npm package @fastify/express: from 4.0.7, fixed in 4.0.10
Fixed versions: 4.0.10.
Conditions (all must be true for the bug to be hit):
- @fastify/express versions 4.0.7 through 4.0.9 (affected range >= 4.0.7, < 4.0.10) (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-84w6-xrf3-f8q8)
- Plugin registered under a parameterized prefix, such as /tenant/:tenantId (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-84w6-xrf3-f8q8)
- Middleware mounted with a RegExp path inside that plugin (source: https://github.com/fastify/fastify-express/security/advisories/GHSA-84w6-xrf3-f8q8)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-133867 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133867 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fastify/fastify-express/security/advisories/GHSA-84w6-xrf3-f8q8
- https://cna.openjsf.org/security-advisories.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133867
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133867"}.

Affected versions

cve.now Index

41Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure22/25Default setups, reachable over the network without a login
  • Reach10/20Affects npm packages
  • Severity9.1/10CVSS 9.1
  • No patch0/5No signal

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active

Impact

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · fastify/fastify-express · Advisory GHSA-84w6-xrf3-f8q8
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133867
RecordNVD · CVE-2026-133867
Other links 1
Linkcna.openjsf.org · security-advisories.html

Questions about CVE-2026-133867

Is CVE-2026-133867 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

When a plugin is registered under a parameterized prefix such as /tenant/:tenantId, middleware mounted with a RegExp path inside that plugin can be skipped. Authentication or authorization middleware meant to guard protected routes may then not run, so unauthenticated clients can reach those routes.

Source: github.com

Which versions are affected by CVE-2026-133867?

@fastify/express (npm): from 4.0.7 before 4.0.10.

Source: cve.now feed data

Am I affected, and how do I check?

Versions 4.0.7 through 4.0.9 of @fastify/express (range >= 4.0.7, < 4.0.10) are affected, in setups that register a plugin under a parameterized prefix and mount a RegExp-path middleware inside it. Check the installed @fastify/express version in your lockfile or with npm ls @fastify/express, and review plugin registrations for parameterized prefixes combined with RegExp middleware paths.

Source: github.com

How do I fix CVE-2026-133867?

Upgrade @fastify/express to 4.0.10, the fixed version.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.