VulnerabilityPublished 10 Sep 2026Updated 26 Oct 2026

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

Affects bump-my-versionSource GCVE Database

Authoritative record:CVE-2026-84381· High 8.1

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

Data as of 26 Oct 2026, 17:56 UTC

CVSS 3.1 base score

8.1High

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.5.1_1

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
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 bump-my-version to 1.5.1_1.

Affected software

Product	Affected	Fixed in
Homebrewbump-my-version`pkg:brew/bump-my-version`Other threats	Affected >=1.4.0 <1.5.1_1	Fixed in 1.5.1_1

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 the TLS handshake is correctly performed for wss:// connections through SOCKS5 proxies. If upgrading is not immediately possible, avoid routing wss:// connections through SOCKS proxies and instead use direct secure WebSocket connections or other transports that perform and verify TLS to the WebSocket origin.

Description

HTTPX2 versions 2.6.0 through 2.9.1 and underlying httpcore2 releases 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 data such as authorization headers, cookies, and application messages. An attacker controlling or observing the SOCKS proxy path can intercept or modify this traffic, impersonate the WebSocket server, and inject malicious messages. The issue is fixed in HTTPX2 and httpcore2 version 2.10.0 and later.

Impact

Attackers controlling or observing the SOCKS5 proxy path can read sensitive data such as URL query parameters, authorization headers, cookies, and WebSocket messages that were expected to be protected by TLS. They can also impersonate the WebSocket server by forging responses and inject or alter WebSocket frames. This compromises confidentiality and integrity of the WebSocket communication when routed through a SOCKS5 proxy using affected versions.

Summary

The vulnerability (CVE-2026-84381) arises because httpcore2 does not start TLS for wss:// connections routed through SOCKS5 proxies, unlike https:// connections which correctly initiate TLS. As a result, the WebSocket opening handshake and all subsequent frames are transmitted in plaintext through the proxy. This flaw affects httpcore2 releases before 2.10.0 and HTTPX2 versions 2.6.0 through 2.9.1, exposing sensitive information to anyone controlling or observing the SOCKS proxy. The vulnerability violates RFC 6455, which requires TLS handshake before sending the WebSocket handshake on secure WebSocket connections. The issue is resolved by upgrading to version 2.10.0 or later, where TLS is correctly started for both https and wss origins in SOCKS5 connections.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 17:56 UTC

Technical details

References

Community reviews

Related threats