Skip to main content

CVE-2026-133250@fastify/middie authentication bypass by alternate path

High priorityCritical9.1EPSS not scored yet

CVE-2026-133250 is a authentication bypass by alternate path in @fastify/middie, 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

A second route to a protected function skips the sign-in check. 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

  1. Upgrade @fastify/middie to 9.3.8 or later.
  2. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.

Description from NVD

@fastify/middie is the middleware engine for the Fastify web framework. In versions up to and including 9.3.7, middie matches path-scoped middleware against its own reading of the request path, which can differ from the path Fastify's router uses to dispatch the request. When the two disagree, the router can route a request to a handler covered by a middleware mount while middie skips that middleware, so an unauthenticated client reaches a handler that an authentication, authorization, or rate-limiting middleware was meant to protect, with no special configuration required. The mismatch is triggered by empty parameter or wildcard values, request targets that do not begin with a slash, and literal percent characters in a mount path. The issue is fixed in @fastify/middie 9.3.8, and users should upgrade to 9.3.8 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/middie 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.

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.