Fastify HTTP Proxy cross-site WebSocket hijacking in proxy plugin
- Exploited
- No known exploitation
- Fix
- Fixed in 11.6.10
- Who is exposed
- Not reported
Summary
@fastify/http-proxy, a Fastify plugin that proxies HTTP and WebSocket traffic, drops the browser origin header on WebSocket connections while still forwarding the user's authentication cookie. An attacker can remotely, without logging in, lure a logged-in user to a malicious page that opens a WebSocket through the proxy and then reads or sends messages as that user.
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 7.1.0 up to but not including 11.6.10, when the plugin is registered with websocket support enabled, it opens the upstream WebSocket connection with a header set built by the default header rewriter, which forwards the client cookie but never sets the upstream origin option, so the browser origin header is dropped while the authenticating cookie is forwarded. Many WebSocket servers defend against cross-site hijacking by checking the origin and treat a missing origin as a trusted non-browser client, so behind the proxy that check never sees the foreign origin. A malicious page visited by a logged-in user can therefore open a WebSocket through the proxy to an upstream that authenticates the handshake with a cookie, and read or send messages on the user's behalf. The issue is fixed in @fastify/http-proxy 11.6.10, and users should upgrade to 11.6.10 or later. As a workaround, provide a header rewriter that sets a correct origin, or validate the origin before the proxy.
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-133111 (@fastify/http-proxy vulnerable to Cross-Site WebSocket Hijacking via dropped Origin header), 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-133111 (entry last updated 2026-11-19):
Affected:
- npm package @fastify/http-proxy: from 7.1.0, fixed in 11.6.10
Fixed versions: 11.6.10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133111 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133111 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-w3r4-6w5h-3vrc
- 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-133111
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-133111"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach12/20@fastify/http-proxy: 549.5K downloads a week
- Severity5.9/10CVSS 5.9
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 40 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: no · 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-w3r4-6w5h-3vrc |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133111 |
| Record | NVD · CVE-2026-133111 |
| Other links 1 | |
| Link | cna.openjsf.org · security-advisories.html |
Questions about CVE-2026-133111
Is CVE-2026-133111 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
Which versions are affected by CVE-2026-133111?
@fastify/http-proxy (npm): from 7.1.0 before 11.6.10.
Source: cve.now feed data
How do I fix CVE-2026-133111?
Upgrade to a fixed version: 11.6.10.
Source: cve.now feed data
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-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-16117@fastify/http-proxy vulnerable to prefix escape via URL-encoded characters
No corrections so far. Something wrong on this page? Report an error.