CVE-2026-129500
High 7.5No known exploitationFix available@fastify/http-proxy vulnerable to Denial of Service via unhandled error on the WebSocket upgrade socket
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 31% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
@fastify/http-proxy is a Fastify plugin that proxies HTTP and WebSocket traffic to an upstream server. In versions from 9.0.0 up to but not including 11.6.10, when the plugin is registered with websocket support enabled, it takes every upgraded socket and dispatches the request through the Fastify router before the WebSocket library takes ownership of the socket. Node.js removes its own error listener from the socket before emitting the upgrade event, and the plugin does not attach one of its own during routing, so a socket error such as a client connection reset that arrives before the WebSocket library takes over is unhandled and terminates the Node.js process. The error window is open whenever anything asynchronous runs between dispatch and the route handler, such as an async hook on the proxied route or any unrelated async route in the application. A single unauthenticated upgrade request followed by a connection reset is enough to crash the server, and it can be repeated to keep the process down. The issue is fixed in @fastify/http-proxy 11.6.10, and users should upgrade to 11.6.10 or later.
Weakness: CWE-248
Patching and mitigation
- Patch status
- Fix available (source: CVE record (openjs))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| @fastify/http-proxy | @fastify/http-proxy | from 9.0.0 before 11.6.10 | 11.6.10 | CVE Program |
| @fastify/http-proxy | @fastify/http-proxy (unaffected) | 11.6.10 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by openjs
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (openjs)