OR
          *cpe:2.3:a:fastify:fastify/middie:*:*:*:*:*:node.js:*:* versions from (including) 9.1.0 up to (excluding) 9.3.3

openjs: https://cna.openjsf.org/security-advisories.html Types: Vendor Advisory

openjs: https://github.com/fastify/middie/security/advisories/GHSA-qcc9-jh8q-47vh Types: Mitigation, Vendor Advisory

{"timestamp":"2026-07-01T11:59:20.488708Z","id":"CVE-2026-14181","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}

@fastify/middie versions 9.1.0 through 9.3.2 fail to guard the URL normalization step used by the standalone engine when incoming request paths contain malformed percent-encoded sequences. Inputs such as an incomplete percent escape or a truncated multibyte sequence cause the underlying decoder to throw synchronously, and the exception escapes the middie normalize step and terminates the Node.js process. The bypass affects applications that call middie.run directly on the standalone engine API, causing an immediate denial of service for all connected clients until restart. Applications using the Fastify plugin path are not affected because Fastifys error handler catches the exception. Patches: upgrade to @fastify/middie 9.3.3. Workarounds: migrate from the standalone engine API to the Fastify plugin path, where the framework error handler catches the exception.

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CWE-248

https://cna.openjsf.org/security-advisories.html

https://github.com/fastify/middie/security/advisories/GHSA-qcc9-jh8q-47vh

[{"vendor":"@fastify/middie","product":"@fastify/middie","defaultStatus":"unaffected","packageURL":"pkg:npm/@fastify/middie","versions":[{"version":"9.1.0","lessThan":"9.3.3","versionType":"semver","status":"affected"},{"version":"9.3.3","versionType":"semver","status":"unaffected"}]}]