Skip to main content
VulnerabilityPublished

CVE-2026-129500: @fastify/http-proxy · Uncaught Exception

Affects @fastify/http-proxySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 11.6.10 soon.

Data as of 19 Nov 2026, 18:36 UTC

CVSS 3.1 base score
7.5High
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.5
Patch
Available – fixed in 11.6.10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 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 18 Nov 2026.

What to do

Upgrade @fastify/http-proxy to 11.6.10.

Affected software

ProductAffectedFixed in
@fastify/http-proxy@fastify/http-proxyAffected
  • >=9.0.0 <11.6.10
Fixed in
  • 11.6.10
npm@fastify/http-proxypkg:npm/@fastify/http-proxyOther threatsAffected
  • >=9.0.0 <11.6.10
Fixed in
  • 11.6.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/http-proxy to version 11.6.10 or later, where this issue is fixed. No other mitigations are indicated by the vendor advisory.

Description

@fastify/http-proxy versions 9.0.0 up to but not including 11.6.10 contain an uncaught exception vulnerability when websocket support is enabled. An unauthenticated client can send an upgrade request followed by a connection reset, causing an unhandled socket error that crashes the Node.js process. This denial-of-service condition can be repeatedly triggered to keep the server down. The issue is fixed in version 11.6.10.

References

Community reviews

Loading reviews…