Fastify HTTP Proxy denial of service in WebSocket upgrade handling
Affects @fastify/http-proxy from 9.4.0 before 11.6.10 when websocket support is enabled (websocket: true). 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 plugin for Fastify can be crashed remotely, without logging in, when WebSocket support is enabled. A single WebSocket upgrade request whose path includes a URL fragment, followed by one frame, terminates the Node.js process, and the attack can be repeated to keep the server down.
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.4.0 up to but not including 11.6.10, when the plugin is registered with websocket support enabled, a WebSocket upgrade request whose path carries a URL fragment is matched by the router and answered with a successful upgrade before the upstream link is created. Building the upstream target then throws, the error is only logged, and the accepted client socket is left open with no error listener, so the next frame the client sends becomes an unhandled error and terminates the Node.js process. A request target that is not a valid URL reference reaching a parameterized prefix triggers the same path. A single unauthenticated upgrade request followed by one frame 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 from 9.4.0 before 11.6.10 with WebSocket support enabled, such as Fastify services proxying WebSocket traffic upstream.
“Applications are affected when websocket: true is used.”
What to do
Upgrade to a fixed version: 11.6.10.
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-129502 (@fastify/http-proxy vulnerable to Denial of Service via a URL fragment in a 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-129502 (entry last updated 2026-11-19):
Affected:
- npm package @fastify/http-proxy: from 9.4.0, fixed in 11.6.10
Fixed versions: 11.6.10.
Conditions (all must be true for the bug to be hit):
- The plugin is registered with websocket support enabled (websocket: true). (source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-29w6-p7r8-xmf9)
- The upgrade request target is not a valid URL reference, such as one with a fragment or a malformed host, reaching a parameterized prefix (with ignoreDuplicateSlashes enabled in the example). (source: https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-29w6-p7r8-xmf9)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129502 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129502 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-29w6-p7r8-xmf9
- 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-129502
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-129502"}.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-29w6-p7r8-xmf9 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129502 |
| Record | NVD · CVE-2026-129502 |
| Other links 1 | |
| Link | cna.openjsf.org · security-advisories.html |
Questions about CVE-2026-129502
Is CVE-2026-129502 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 unauthenticated remote client can send a WebSocket upgrade request whose target is not a valid URL reference, such as one with a fragment or a malformed host. The next frame the client sends then triggers an unhandled error that terminates the Node.js process, and the crash can be repeated.
Source: github.com
Which versions are affected by CVE-2026-129502?
@fastify/http-proxy (npm): from 9.4.0 before 11.6.10.
Source: cve.now feed data
Am I affected, and how do I check?
Versions from 9.4.0 before 11.6.10 are affected when the plugin is registered with websocket: true. Check the installed version with npm ls @fastify/http-proxy and look for websocket: true in the plugin registration. The crash path also needs a non-valid upgrade request target reaching a parameterized prefix, with ignoreDuplicateSlashes enabled in the example.
Source: github.com
How do I fix CVE-2026-129502?
Upgrade @fastify/http-proxy to 11.6.10 or later, which is the fixed version listed for this vulnerability.
Source: github.com
Related
- CVE-2026-33805@fastify/reply-from vulnerable to connection header abuse enabling stripping of proxy-added headers
- CVE-2026-129500@fastify/http-proxy vulnerable to Denial of Service via unhandled error on the WebSocket upgrade socket
- 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.