Read the docs
TI-2026-69323 Aliases CVE-2026-107284

AsyncHttpClient WebSocket handshake proceeds after failed accept check

Priority LOW 17CWE-345Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
None · Low · None
Fix status
Partial Red Hat: 1 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-345.

Summary

From 3.0.0 before 3.0.12 and from 2.0.0 before 2.16.1, AsyncHttpClient async-http-client continues a WebSocket handshake after rejecting a missing or invalid Sec-WebSocket-Accept value. WebSocketHandler.upgrade installs the pipeline and delivers onOpen anyway, so frames sent with the invalid 101 response can be delivered from a peer that did not prove the handshake (CWE-345). A remote peer with no privileges can trigger this.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Description from the CNA

The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. Prior to 3.0.12 and 2.16.1, WebSocketHandler.upgrade aborts a handshake whose Sec-WebSocket-Accept value is missing or invalid but continues into pipeline installation and onOpen delivery. Frames coalesced with the invalid 101 response can be decoded and delivered from a peer that did not prove the handshake, although the request future fails and the channel closes. This issue is fixed in versions 3.0.12 and 2.16.1.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00138 3rd percentileScored 2026-11-07
Fix Partial async-http-client (AsyncHttpClient): 3.0.12, 2.16.1Red Hat: 1 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
AsyncHttpClientasync-http-client3.0.0 to before 3.0.12; 2.0.0 to before 2.16.13.0.12, 2.16.1Patch availableCNA
  • async-http-client VendorAsyncHttpClient Affected 3.0.0 to before 3.0.12; 2.0.0 to before 2.16.1 Fixed in 3.0.12, 2.16.1 Patch available CNA

Remediation

Upgrade async-http-client to 3.0.12 or 2.16.1, which fix this issue. Red Hat lists Red Hat Fuse 7 as affected with no fix planned.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

  • Fix · CNA async-http-client (AsyncHttpClient) Fixed in 3.0.12, 2.16.1

Vendor assessments

Red Hat

Red Hat rating: Low. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Fuse 7AffectedNo fix planned: Out of support scope

Timeline

  1. 2026-10-07 Threatist record created from CVE-2026-107284
  2. 2026-10-08 CISA SSVC decision points changed
  3. 2026-11-03 Affected versions changed · Red Hat
  4. 2026-11-03 CVSS score added · Red Hat

References

Other 5

  • TI-2024-36149 AsyncHttpClient (AHC) library's `CookieStore` replaces explicitly defined `Cookie`s CVSS 4.0CRITICAL 9.2
  • TI-2026-69321 Cross-host replay in AsyncHttpClient leaks credentials to new host CVSS 4.0CRITICAL 9.4
  • TI-2026-69315 AsyncHttpClient sends passwords in cleartext after Digest downgrade CVSS 4.0HIGH 8.7
  • TI-2026-58825 AsyncHttpClient: Unbounded HTTP/1.1 response decompression enables a decompression-bomb denial of service CVSS 3.1HIGH 7.5
  • TI-2026-69311 Unbounded WebSocket decompression in AsyncHttpClient enables DoS CVSS 3.1HIGH 7.5
  • TI-2026-58823 AsyncHttpClient: SOCKS proxy credentials sent to the origin server over plaintext HTTP CVSS 3.1HIGH 7.5
See all 23 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences