@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.
CVE-2026-14198
This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EPSS
- 21.7%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 2, 2026
Advisory Details (2)
Auto-updated Jul 1, 2026@fastify/middie vulnerable to authorization bypass via encoded slash in path parameter values · Advisory · fastify/middie · GitHub
https://github.com/fastify/middie/security/advisories/GHSA-2v46-jxjm-7q3vSecurity Advisories | OpenJS Foundation CVE Numbering Authority
https://cna.openjsf.org/security-advisories.htmlWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 45× in last 7d / 66× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-11 20:59 UTCEG score recompute
- 2026-07-11 16:36 UTCEG score recompute
- 2026-07-11 12:12 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 07:49 UTCEG score recompute
- 2026-07-11 03:25 UTCEG score recompute
- 2026-07-10 23:01 UTCEG score recompute
- 2026-07-10 18:37 UTCEG score recompute
- 2026-07-10 14:13 UTCEG score recompute
- 2026-07-10 09:46 UTCEG score recompute
- 2026-07-10 05:18 UTCEG score recompute
- 2026-07-10 00:53 UTCEG score recompute
- 2026-07-09 20:25 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 16:01 UTCEG score recompute
- 2026-07-09 11:37 UTCEG score recompute
- 2026-07-09 07:13 UTCEG score recompute
- 2026-07-09 02:50 UTCEG score recompute
- 2026-07-08 22:27 UTCEG score recompute
- 2026-07-08 18:03 UTCEG score recompute
- 2026-07-08 13:40 UTCEG score recompute
- 2026-07-08 09:16 UTCEG score recompute
- 2026-07-08 04:53 UTCEG score recompute
- 2026-07-08 00:21 UTCEG score recompute
- 2026-07-07 19:57 UTCEG score recompute
Show 41 moreShow fewer
- 2026-07-07 15:33 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 11:07 UTCEG score recompute
- 2026-07-07 06:43 UTCEG score recompute
- 2026-07-07 02:15 UTCEG score recompute
- 2026-07-06 21:47 UTCEG score recompute
- 2026-07-06 17:24 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 12:57 UTCEG score recompute
- 2026-07-06 08:33 UTCEG score recompute
- 2026-07-06 04:05 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 23:40 UTCEG score recompute
- 2026-07-05 19:17 UTCEG score recompute
- 2026-07-05 14:53 UTCEG score recompute
- 2026-07-05 10:28 UTCEG score recompute
- 2026-07-05 06:05 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 01:40 UTCEG score recompute
- 2026-07-04 21:18 UTCEG score recompute
- 2026-07-04 16:54 UTCEG score recompute
- 2026-07-04 12:31 UTCEG score recompute
- 2026-07-04 08:08 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 03:41 UTCEG score recompute
- 2026-07-03 23:10 UTCEG score recompute
- 2026-07-03 18:39 UTCEG score recompute
- 2026-07-03 14:16 UTCEG score recompute
- 2026-07-03 09:53 UTCEG score recompute
- 2026-07-03 05:29 UTCEG score recompute
- 2026-07-03 01:02 UTCEG score recompute
- 2026-07-02 20:38 UTCEG score recompute
- 2026-07-02 16:14 UTCEG score recompute
- 2026-07-02 11:51 UTCEG score recompute
- 2026-07-02 07:27 UTCEG score recompute
- 2026-07-02 03:04 UTCEG score recompute
- 2026-07-01 22:40 UTCEG score recompute
- 2026-07-01 18:17 UTCEG score recompute
- 2026-07-01 13:53 UTCEG score recompute
- 2026-07-01 13:52 UTCNVD updatefirst tracked
Frequently asked(5)
What is CVE-2026-14198?
When was CVE-2026-14198 disclosed?
Is CVE-2026-14198 actively exploited?
What is the CVSS score of CVE-2026-14198?
How do I remediate CVE-2026-14198?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-14198
Is Your Infrastructure Affected by CVE-2026-14198?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.