CRITICAL🇵🇱 Wersja polska

CVE-2026-14198

CVSS 9.1v3.1pub. 2026-07-01upd. 2026-07-02

@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.

🤖 AI Analysis
How it works

The @fastify/middie layer decodes the encoded slash %2F in path parameter values before matching against registered middleware paths. However, the Fastify router preserves the original encoding during route lookup. Both layers interpret the same path differently — the middleware does not recognize the request as matching its pattern and does not execute, while the route handler is invoked normally. An attacker only needs to send a crafted URL with %2F in place of a parameter — the HTTP method and additional preconditions are irrelevant.

Impact

An unauthenticated attacker can bypass middleware responsible for authentication, authorization, rate limiting, or auditing and gain direct access to a protected handler. This can result in violations of application data confidentiality and integrity.

Mitigation & patch

Update @fastify/middie to version 9.3.3. As a temporary workaround: avoid using parameterized middleware paths for security decisions, and move authentication and authorization to the route handler or to a Fastify hook executed after route resolution by the router.

Who is affected

@fastify/middie in versions 9.1.0 to 9.3.2 (product: Fastify/Middie)

Analysis generated by Claude AI (Anthropic) based on NVD data. Always verify with vendor.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • Fastify Fastify\/middie

    APP
    Fastify
    9.1.0 – 9.3.3 (excl.)
🔵
CHECK WITH VENDOR
No clear patch data available. Check vendor references.
CWE
References

Related vulnerabilities

CVE-2026-6270CRITICAL9.1PL ✓same product

Pominięcie uwierzytelnienia w @fastify/middie — brak dziedziczenia middleware

CVE-2026-14181HIGH7.5PL ✓same product

DoS w @fastify/middie — nieobsłużony wyjątek przy zniekształconych URL powoduje crash procesu

CVE-2026-33804HIGH7.4same product

@fastify/middie versions 9.3.1 and earlier are vulnerable to middleware bypass when the deprecated Fastify ign...

CVE-2026-2880HIGH8.2same product

A vulnerability in @fastify/middie versions < 9.2.0 can result in authentication/authorization bypass when usi...

CVE-2026-22031HIGH8.4same product

@fastify/middie is the plugin that adds middleware support on steroids to Fastify. A security vulnerability ex...