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.
- Exploited
- No known exploitation
- Fix
- Fixed in 11.6.10
- Who is exposed
- Not reported
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
Original 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.
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.
“Applications are affected when websocket: true is used over a cleartext HTTP/1 listener.”
What to do
Upgrade to a fixed version: 11.6.10.
Workaround: Terminate TLS in front of the proxy so upgrades arrive on a TLSSocket, which is not affected
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach12/20@fastify/http-proxy: 549.5K downloads a week
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
- Would score about 45 if advisories confirm default setups are exposed
Impact
- Widely used@fastify/http-proxy has 549.5k weekly downloads. npmjs.com
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · fastify/fastify-http-proxy · Advisory GHSA-q659-79j2-32h5 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129500 |
| Record | NVD · CVE-2026-129500 |
| Other links 1 | |
| Link | cna.openjsf.org · security-advisories.html |
Questions about CVE-2026-129500
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: cve.now feed data
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: github.com
Which versions are affected by CVE-2026-129500?
@fastify/http-proxy (npm): from 9.0.0 before 11.6.10.
Source: cve.now feed data
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: github.com
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: github.com
Related
- CVE-2026-33805@fastify/reply-from vulnerable to connection header abuse enabling stripping of proxy-added headers
- CVE-2026-129502@fastify/http-proxy vulnerable to Denial of Service via a URL fragment in a WebSocket upgrade
- CVE-2026-130647@fastify/http-proxy vulnerable to Denial of Service via a pipelined WebSocket upgrade
- CVE-2026-127060@fastify/http-proxy vulnerable to prefix escape via semicolon path-parameter dot-segments
- CVE-2026-133111@fastify/http-proxy vulnerable to Cross-Site WebSocket Hijacking via dropped Origin header
- CVE-2026-16117@fastify/http-proxy vulnerable to prefix escape via URL-encoded characters
No corrections so far. Something wrong on this page? Report an error.