CVE-2026-129500: @fastify/http-proxy vulnerable to Denial of Service via unhandled error on the WebSocket upgrade socket
@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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@fastify/http-proxyto a version that resolves this vulnerability.Fixed in 11.6.10
Event History
Frequently Asked Questions
Which deployments are exposed to this denial-of-service condition?
Deployments using @fastify/http-proxy versions 9.0.0 through 11.6.9 are affected when the plugin is registered with WebSocket support enabled. The error window exists when asynchronous work occurs between upgrade-request dispatch and the proxied route handler, including an async hook on that route or an unrelated async route in the application.
What must an attacker do to trigger the crash?
An unauthenticated attacker only needs to send a WebSocket upgrade request and then reset the connection while the socket is in the routing window before the WebSocket library takes ownership. A single request can terminate the Node.js process, and repeated requests can keep it unavailable.
What should teams do if they cannot upgrade immediately?
The provided data identifies upgrading to @fastify/http-proxy 11.6.10 or later as the remediation. It does not provide a validated workaround for affected deployments that cannot patch immediately.