CVE-2026-14198
@fastify/middie vulnerable to authorization bypass via encoded slash in path parameter values
Description
@fastify/middie versions 9.1.0 through 9.3.2 decode the encoded slash %2F inside path parameter values before matching middleware paths, while Fastify's underlying router preserves the encoding during route lookup. The two layers disagree on the canonical request path, so the middleware fails to match a URL that the route handler does match. When middleware is used for authentication, authorization, rate limiting, or auditing on parameterized paths, an attacker can reach the protected handler by sending a single crafted URL with an encoded slash in the parameter position. The bypass is HTTP method agnostic and requires no authentication or special preconditions. Patches: upgrade to @fastify/middie 9.3.3. Workarounds: avoid parameterized middleware paths for security decisions, or enforce authentication at the route handler or via a Fastify hook that runs after the router has resolved the request.
INFO
Published Date :
July 1, 2026, 11:29 a.m.
Last Modified :
July 1, 2026, 11:29 a.m.
Remotely Exploit :
No
Source :
openjs
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | CRITICAL | ce714d77-add3-4f53-aff5-83d477b104bb |
Solution
- Upgrade @fastify/middie to version 9.3.3.
- Avoid parameterized middleware paths for security.
- Enforce security checks at route handlers.
- Use Fastify hooks after router resolution.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-14198 vulnerability anywhere in the article.