CVE-2026-129502: @fastify/http-proxy · Uncaught Exception
Affects @fastify/http-proxySource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 11.6.10 soon.
Data as of 19 Nov 2026, 18:36 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 7.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:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| @fastify/http-proxy@fastify/http-proxy | Affected
| Fixed in
|
npm@fastify/http-proxypkg:npm/@fastify/http-proxyOther threats | Affected
| Fixed in
|
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 vulnerability is fixed. No other mitigations are indicated by the vendor advisory.
Description
@fastify/http-proxy versions 9.4.0 up to but not including 11.6.10 contain a vulnerability where a WebSocket upgrade request with a URL fragment causes an unhandled exception. This leads to the Node.js process crashing due to an unhandled error after the client socket is left open without an error listener. The flaw allows unauthenticated attackers to crash the server with a single crafted request. The issue is fixed in version 11.6.10.