Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Unrated

Authorization Bypass in @fastify/middie via Encoded Slash Path Canonicalization Mismatch

IdentifiersCVE-2026-14198CWE-178

CVE-2026-14198 affects @fastify/middie versions 9.1.0 through 9.3.2. The vulnerability is caused by inconsistent path canonicalization between @fastify/middie and Fastify's underlying router. Specifically, @fastify/middie decodes encoded slashes (%2F) inside path parameter values before matching middleware paths, while the router preserves the encoded value during route lookup. Because the middleware layer and router evaluate different effective paths, middleware attached to parameterized paths may fail to run even though the corresponding route handler is successfully matched and executed. In deployments where middleware on parameterized paths is relied upon for authentication, authorization, rate limiting, or auditing, an attacker can send a crafted request containing an encoded slash in the parameter position to bypass those middleware-enforced controls and reach the protected handler.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow unauthenticated attackers to bypass middleware-based security controls on affected parameterized paths. Depending on how the application uses @fastify/middie, this may result in unauthorized access to protected endpoints, bypass of authorization checks, evasion of rate limiting, and loss of audit or logging coverage. The impact is especially severe where authentication or authorization is enforced only in middleware rather than at the route handler or in a post-routing hook.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, avoid using parameterized middleware paths for security decisions. Enforce authentication and authorization at the route handler itself or via a Fastify hook that executes after the router has resolved the request, so both security checks and route dispatch operate on the same canonical path interpretation. Also review rate limiting and auditing logic implemented in middleware on parameterized paths, as those controls may be bypassed as well.

Remediation

Patch, then assume compromise.

Upgrade @fastify/middie to version 9.3.3, which contains the patch for this path matching and decoding inconsistency. Review applications for any security-sensitive middleware mounted on parameterized paths and validate that access control behavior remains correct after upgrading.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity9

Community discussion across Reddit, Mastodon, and other social sources.