CVE-2026-133111
Description
A flaw was found in @fastify/http-proxy. When WebSocket support is enabled, the proxy forwards client authentication cookies to the upstream server but drops the browser Origin header. A remote attacker can exploit this by tricking an authenticated user into visiting a malicious webpage that initiates a WebSocket connection through the proxy. Because the upstream server cannot verify the request origin, the connection is trusted, allowing the attacker to read or send messages on the victim's behalf.
Statement
This vulnerability is rated as having Moderate impact for Red Hat environments because exploitation depends on a victim visiting a malicious website while actively authenticated, alongside backend WebSocket services that implicitly trust handshakes missing the Origin header. In typical proxy configurations, cross-site WebSocket hijacking allows an attacker to interact with backend endpoints under the context of the authenticated user. However, the attack requires specific upstream authentication patterns relying on session cookies and cannot be executed autonomously without victim interaction, constraining overall severity.
Mitigation
To mitigate this issue through configuration:
1. Validate the Origin header on incoming handshake requests before passing traffic to the proxy, rejecting requests that originate from unexpected or untrusted domains.
2. Configure a custom header rewriter function in the proxy options to ensure the client's Origin header is explicitly retained and passed to the upstream server during WebSocket handshakes.
3. If WebSocket forwarding is not required by the application, disable WebSocket handling within the plugin configuration.
Note: Modifying application configuration requires restarting or reloading the affected service, which will temporarily terminate active network sessions.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.9 | N/A | 5.9 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N
Understanding the Weakness (CWE)
Access Control,Other
Technical Impact: Gain Privileges or Assume Identity; Varies by Context; Bypass Protection Mechanism
An attacker from an untrusted origin could successfully establish a communication channel. The attacker could then gain privileges and access unexpected functionality that was only intended for trusted sources.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.