GitHub Advisoryadvisory · Maven
GHSA-3wp9-xfwm-rjjf AsyncHttpClient: WebSocket proxy credentials sent to the origin server over a CONNECT tunnel
MEDIUM
Official page ↗
- Aliases
- CVE-2026-107285
- Ecosystem
- Maven
- Packages
- org.asynchttpclient:async-http-client
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weaknesses
- CWE-319, CWE-522
- Reviewed
- 2026-10-08
Affected packages
• Maven org.asynchttpclient:async-http-client: >= 3.0.0, < 3.0.12 → fixed in 3.0.12
• Maven org.asynchttpclient:async-http-client: >= 2.0.0, < 2.16.1 → fixed in 2.16.1
Description
Impact
When a ws:// request is routed through an HTTP proxy with proxy authentication configured, the client tunnels the connection with an HTTP CONNECT, the same as it does for https://. Once the tunnel is open, the WebSocket upgrade request that follows is sent through the tunnel directly to the origin server, not to the proxy. The proxy-auth gate and the companion request-target selection keyed only on whether the URI was secured, which is false for ws://, so the tunnelled upgrade request incorrectly carried the proxy's Proxy-Authorization header and an absolute-form request target meant for the proxy. Any origin server reached over a proxied ws:// connection, or anyone positioned on the origin side of the wire, could recover the proxy credentials: directly for Basic, or as a replayable and offline-crackable response for Digest.
Affected versions
• 3.x: up to and including 3.0.11
• 2.x: up to and including 2.16.0
Patches
Fixed in 3.0.12 on the 3.x line and in 2.16.1 on the 2.x line. The preemptive Proxy-Authorization header and the absolute-form request target are no longer attached to a tunnelled ws:// upgrade; a ws:// request is now treated like wss://.
Workarounds
Do not use proxy authentication together with ws:// requests through an HTTP proxy, or use wss:// instead.
Details
The proxy-auth gate in NettyRequestFactory#newNettyRequest and the sibling branch in requestUri() did not exclude WebSocket URIs, even though the CONNECT-tunnelling check in NettyRequestSender already tunnels ws:// through CONNECT exactly like https://.
Note that 3.0.12 is itself affected by a separate issue, GHSA-rqf5-2wxv-rjf4, where a Digest challenge the client cannot read downgrades to Basic and sends the password in cleartext. Upgrade to 3.0.13 to pick up both fixes.
Related
Alias · CVE (1)
- CVE-2026-107285 The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. vulnerability
References
- https://github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-3wp9-xfwm-rjjf web
- https://nvd.nist.gov/vuln/detail/CVE-2026-107285 advisory
- https://github.com/AsyncHttpClient/async-http-client/commit/6e9cb75a9b7259353f983fc90ca28b1da3742e18 web
- https://github.com/AsyncHttpClient/async-http-client/commit/c4feab0f7f86d61505a48e40d383c8a375a22e18 web
- https://github.com/AsyncHttpClient/async-http-client package
- https://github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-2.16.1 web
- https://github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-3.0.12 web