Live › vulnerability › CVE-2026-112712
Go to dashboardIn @fastify/middie versions 9.0.0 through 9.3.5, path-scoped middleware can be silently skipped while the route handler still runs. An unauthenticated request can therefore bypass authentication, authorization, or rate limiting that was attached as middleware.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Check the installed version: npm ls @fastify/middie
9.3.6 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
@fastify/middie is the Express-style middleware engine for Fastify. In versions from 9.0.0 through 9.3.5, the use() function joined a path-scoped middleware's mount path to the plugin scope prefix in a way that could diverge from the path Fastify's router serves, most often when the scope prefix ended in a slash, and also for array mount paths and for mount paths written without a leading slash. When the two paths disagreed, the middleware was silently skipped while the route handler still ran, so path-scoped middleware such as authentication, authorization, or rate limiting could be bypassed by a single unauthenticated request. The issue is fixed in @fastify/middie 9.3.6, and users should upgrade to 9.3.6 or later. As a workaround, enforce authorization in a Fastify hook such as preHandler that runs after the router has resolved the request.
This page as .md · .json · in your agent: get_signal("CVE-2026-112712")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.