VulnerabilityPublished 10 Sep 2026Updated 31 Oct 2026

CVE-2026-84381: HTTPX2 · Secure WebSocket traffic sent without TLS through SOCKS proxies

Affects rapid-mlxSource GCVE Database

Compare

Authoritative record:CVE-2026-84381· High 8.1

Not known to be exploited · CVSS 8.1 High : upgrade to 0.12.8 soon.

Data as of 1 Nov 2026, 00:35 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 0.12.8

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade rapid-mlx to 0.12.8.

Affected software

Product	Affected	Fixed in
Homebrewrapid-mlx`pkg:brew/rapid-mlx`Other threats	Affected >=0.11.3 <0.12.8	Fixed in 0.12.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade HTTPX2 and httpcore2 to version 2.10.0 or later, where TLS is correctly started for both https and wss origins over SOCKS5 proxies. If immediate upgrade is not possible, avoid routing wss:// connections through SOCKS proxies. Instead, use direct secure WebSocket connections or alternative transports that perform and verify TLS to the WebSocket origin.

Description

HTTPX2 versions 2.6.0 through 2.9.1 and underlying httpcore2 before 2.10.0 do not initiate TLS for secure WebSocket (wss://) connections routed through SOCKS5 proxies. This results in the WebSocket handshake and subsequent frames being sent in plaintext through the proxy, exposing sensitive headers, cookies, and messages. An attacker controlling or observing the SOCKS proxy can intercept or modify this traffic, violating the expected confidentiality and integrity of wss connections. The issue is fixed in HTTPX2 and httpcore2 version 2.10.0 and later.

Impact

An attacker controlling or monitoring the SOCKS5 proxy path can intercept sensitive information including URL query parameters, authorization headers, cookies, and WebSocket application messages that were expected to be protected by TLS. Because no TLS handshake or certificate verification occurs, the attacker can impersonate the WebSocket server and inject or modify WebSocket frames. This compromises confidentiality and integrity of wss connections routed through SOCKS proxies. Direct wss connections and https requests through SOCKS are not affected.

Summary

The vulnerability in httpcore2 before version 2.10.0 causes TLS not to start for wss:// connections routed through SOCKS5 proxies. HTTPX2 versions 2.6.0 through 2.9.1 expose this flaw via their websocket client APIs. The SOCKS5 connection implementation upgrades to TLS only for https schemes, omitting wss. Consequently, the WebSocket opening handshake and all frames are transmitted in plaintext through the proxy. This allows a malicious or compromised SOCKS proxy to observe or manipulate sensitive data such as URL query parameters, authorization headers, cookies, and WebSocket messages. The flaw violates RFC 6455 requirements for secure WebSocket connections. The issue is resolved by upgrading to version 2.10.0 or later, which correctly initiates TLS for both https and wss origins over SOCKS5.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Nov 2026, 00:35 UTC

Technical details

References

Community reviews

Related threats