PULSE
FEED
ransommedusalocker reclama a F5A · MF · Technologyransomsafepay reclama a tiic.com.ph · PH · Otherransomsafepay reclama a threeroyal.com · TW · Otherransomsafepay reclama a factotal.com · CL · Technologyransomsafepay reclama a offshore-ocs.com · SG · Otherransomsafepay reclama a relax.es · ES · Hospitalityransomsafepay reclama a pacifico.com.ar · AR · Financial Servicesransomsafepay reclama a qrc-solutions.com · EC · Professional Servicesransomsafepay reclama a santak.com.sg · SG · Energy & Utilitiesransomsafepay reclama a themedical.co.il · IL · Healthcareransomosiris reclama a Kang Chiao International School (Linkou) · TW · Educationransomincransom reclama a Regions Behavioral Hospital · US · Healthcareransomsoulgroup reclama a County government within a U.S. state · US · Government & Defenseransomlockbit5 reclama a genica.com.ve · VE · Otherransommedusalocker reclama a F5A · MF · Technologyransomsafepay reclama a tiic.com.ph · PH · Otherransomsafepay reclama a threeroyal.com · TW · Otherransomsafepay reclama a factotal.com · CL · Technologyransomsafepay reclama a offshore-ocs.com · SG · Otherransomsafepay reclama a relax.es · ES · Hospitalityransomsafepay reclama a pacifico.com.ar · AR · Financial Servicesransomsafepay reclama a qrc-solutions.com · EC · Professional Servicesransomsafepay reclama a santak.com.sg · SG · Energy & Utilitiesransomsafepay reclama a themedical.co.il · IL · Healthcareransomosiris reclama a Kang Chiao International School (Linkou) · TW · Educationransomincransom reclama a Regions Behavioral Hospital · US · Healthcareransomsoulgroup reclama a County government within a U.S. state · US · Government & Defenseransomlockbit5 reclama a genica.com.ve · VE · Other
← All CVEs
CVE WatchNov 21, 2026

CVE-2026-133120

@fastify/express is a compatibility layer that lets Express middleware run inside the Fastify web framework. In versions before 4.0.10, the

CVSS

9.1

Critical

EPSS

—

KEV

—

Exploit Today

—

0-100

Published: Nov 21, 2026 · Last modified: Nov 21, 2026 · CWE-174 · CWE-436

EPSS · 30d

Not enough EPSS history yet.

Technical description

@fastify/express is a compatibility layer that lets Express middleware run inside the Fastify web framework. In versions before 4.0.10, the plugin passes Express a request URL that does not always match the path Fastify's router dispatched, so path-scoped Express middleware can be skipped while the route handler still runs. Several request forms trigger the mismatch, including percent-decoding that rewrites a backslash to a slash or double-decodes an encoded percent sign, and a request target that begins with an asterisk, so the middleware and the handler disagree on the path or on parameter and query values. An unauthenticated client can therefore reach a handler that an authentication, authorization, or rate-limiting middleware was meant to protect, with no special configuration required. The issue is fixed in @fastify/express 4.0.10, and users should upgrade to 4.0.10 or later.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-1338679.1 CRI
—
———@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.14h
CVE-2026-1332509.1 CRI
—
———@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.14h
CVE-2026-1295049.1 CRI
—
———@fastify/express is a compatibility layer that lets Express middleware run inside the Fastify web framework. In versions 4.0.0 through 4.0.9, the plugin joins a path-scoped middleware's mount path to the Fastify plugin prefix by string concatenation, so when the plugin prefix ends with a slash or the mount path omits its leading slash, the resulting Express mount path does not line up with the route the Fastify router serves. Express then fails to match and passes the request on while the Fastify router still dispatches the route, so the middleware is silently skipped. An application that uses path-scoped Express middleware for authentication or authorization inside a prefixed plugin can expose protected routes to unauthenticated clients, with no crafted request and no non-default option required, and string, array, and regular-expression mount paths are all affected. The issue is fixed in @fastify/express 4.0.10, and users should upgrade to 4.0.10 or later.14h
CVE-2026-1246269.1 CRI
—
———@fastify/express is a compatibility layer that lets Express middleware run inside the Fastify web framework. In versions 4.0.5 through 4.0.9, the plugin matches path-scoped Express middleware with a matcher that requires a non-empty value for a dynamic segment, while Fastify's router accepts an empty parameter or wildcard value. When a route and an Express middleware mount share a dynamic pattern, a request with an empty segment matches the Fastify route and runs the handler while the middleware mounted on that pattern is skipped, so on a scoped mount an unauthenticated request can reach a protected handler. No special configuration is required, and the practical impact depends on what the empty value selects in the application. The issue is fixed in @fastify/express 4.0.10, and users should upgrade to 4.0.10 or later.14h
CVE-2026-121714—
—
——0RabbitMQ is a messaging and streaming broker. In the affected revision identified by the advisory, the AMQP 1.0 server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl stops at the first body section and preserves the remaining bytes in bare_and_footer without validating message-section order. An authenticated publisher with write permission can place a properties section carrying a forged user-id after the body, causing rabbit_access_control:check_user_id/2 to see no user-id while permissive downstream AMQP 1.0 decoders or AMQP 0-9-1 conversion through classic and quorum queues expose the forged identity. Applications that rely on RabbitMQ-validated user-id metadata can therefore accept attacker-controlled publisher attribution. Strict consumers that reject out-of-order sections are not vulnerable to identity spoofing, and the issue does not bypass broker routing or destination authorization. This issue is fixed in version 4.3.5.1d
CVE-2026-945996.1 MED
—
——0NukeViet CMS is a multi Content Management System. From 4.5.00 until 4.5.13 and 4.6.02, an unauthenticated attacker can place a multiply encoded value in the news module search q parameter. $nv_Request->get_title() decodes and sanitizes the input once, but modules/news/funcs/search.php subsequently applies urldecode() after sanitization. The resulting raw keyword reaches the {KEY} search-input attribute through search_theme() and the no-results element through search_result_theme() in the default and mobile themes, permitting attribute or tag injection and same-origin JavaScript execution when a victim opens the crafted search URL. This issue is fixed in versions 4.5.13 and 4.6.02.1d