Skip to content
Threat Brief

← All advisories

CVE-2026-133111

Medium 5.9No known exploitationFix available

@fastify/http-proxy vulnerable to Cross-Site WebSocket Hijacking via dropped Origin header

Record last updated

CVSS score

5.9

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.1%

Higher than 2% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-1385

Patching and mitigation

Patch status
Fix available (source: CVE record (openjs))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
@fastify/http-proxy@fastify/http-proxyfrom 7.1.0 before 11.6.1011.6.10CVE Program
@fastify/http-proxy@fastify/http-proxy (unaffected)11.6.10Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by openjs

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (openjs)

    Source: CVE record (openjs) (opens in a new tab)

Vendor guidance and references