Skip to content
Threat Brief

← All advisories

CVE-2026-130647

High 7.5No known exploitationFix available

@fastify/http-proxy vulnerable to Denial of Service via a pipelined WebSocket upgrade

Record last updated

CVSS score

7.5

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 31% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

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, a WebSocket upgrade that is pipelined behind another HTTP request on the same cleartext connection arrives while that request's response is still attached to the socket. The shared upgrade listener sees the socket is already claimed and returns early without taking the upgrade, but it does not attach an error listener to the raw socket, and Node.js has already removed its own error listener before emitting the upgrade event. A later socket error on that connection, such as a client connection reset, is therefore unhandled and terminates the Node.js process. A single unauthenticated connection that pipelines an upgrade behind a normal request and then resets is enough to crash the server, and it can be repeated to keep the process down. Upgrades over TLS are not affected. 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

VendorProductAffected versionsFixed inPer
@fastify/http-proxy@fastify/http-proxyfrom 9.0.0 before 11.6.1011.6.10CVE Program
@fastify/http-proxy@fastify/http-proxy (unaffected)11.6.10Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by openjs

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (openjs)

    Source: CVE record (openjs) (opens in a new tab)

Vendor guidance and references