Skip to main content
VulnerabilityPublished

CVE-2026-129850: @fastify/express · Improper Handling of Case Sensitivity

Affects @fastify/expressSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High : upgrade to 4.0.10 soon.

Data as of 21 Nov 2026, 17:14 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (openjs)CVSS 3.17.4
Patch
Available – fixed in 4.0.10
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade @fastify/express to 4.0.10.

Affected software

ProductAffectedFixed in
@fastify/express@fastify/expressAffected
  • >=4.0.0 <4.0.10
Fixed in
  • 4.0.10
npm@fastify/expresspkg:npm/@fastify/expressOther threatsAffected
  • >=4.0.0 <4.0.10
Fixed in
  • 4.0.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade @fastify/express to version 4.0.10 or later, where this vulnerability is fixed. Applications should ensure they are not using affected versions with case-insensitive routing enabled. No other mitigations are indicated by the vendor advisory.

Description

@fastify/express versions 4.0.0 through 4.0.9 have a vulnerability in case-insensitive routing where Unicode characters equivalent to ASCII letters bypass path-scoped middleware protections. This allows unauthenticated clients to reach handlers meant to be protected by authentication, authorization, or rate-limiting middleware if case-insensitive routing is enabled and the mount path contains affected letters. The issue is fixed in version 4.0.10.

References

Community reviews

Loading reviews…