CVE-2026-133867@fastify/express improper authentication
CVE-2026-133867 is a improper authentication in @fastify/express, rated critical (9.1 on CVSS 3.1).
Why this priority: Critical, and reachable over the network without an account.
Published · Updated · NVD status: Received
What it is
The software does not prove who a caller is, so an attacker can pass as someone else. Two components read the same input differently, and an attacker exploits the gap.
How it is reached
An attacker can exploit it over the network, without an account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects and change data or behaviour. In practice, this kind of flaw lets an attacker act as a signed-in user, or an administrator, without valid credentials.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade @fastify/express to 4.0.10 or later.
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Description from NVD
@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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Sign-in, session and token handling. The flaw sits between anonymous callers and authenticated sessions.
- Identity providers and SSO. The flaw sits between anonymous callers and authenticated sessions.
- Proxies, load balancers and the servers behind them. The flaw sits between a front-end proxy and its back end.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- Between anonymous callers and authenticated sessions. An attacker who crosses it can act as a signed-in user, or an administrator, without valid credentials.
- Between a front-end proxy and its back end. An attacker who crosses it can smuggle requests past the proxy's checks.
Questions to answer about your own systems
- Where does @fastify/express run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
14-day free trial
Understand how your systems connect.
See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.
Read more
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.