Answer in brief
CVE-2026-85720 records a Medium severity (CVSS 5.9) vulnerability in AsyncHttpClient: Origin credentials sent to the proxy on the plaintext CONNECT request. The current sources do not mark it as known exploited. The current feed maps AsyncHttpClient/async-http-client (generic), org.asynchttpclient:async-http-client (maven), org.asynchttpclient:async-http-client (maven), org.asynchttpclient:async-http-client (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps AsyncHttpClient/async-http-client (generic), org.asynchttpclient:async-http-client (maven), org.asynchttpclient:async-http-client (maven), org.asynchttpclient:async-http-client (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| AsyncHttpClient/async-http-clientgeneric | >= 2.0.0, < 2.16.1 || >= 3.0.0, < 3.0.12 | Not reported |
| org.asynchttpclient:async-http-clientmaven | >=3.0.0,<=3.0.11 | 3.0.12 |
| org.asynchttpclient:async-http-clientmaven | >=2.0.0,<=2.16.0 | 2.16.1 |
| org.asynchttpclient:async-http-clientmaven | >=3.0.0 <3.0.12 | 3.0.12 |
| org.asynchttpclient:async-http-clientmaven | >=2.0.0 <2.16.1 | 2.16.1 |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.0.0 until 2.16.1 and 3.0.12, a request using an HTTP proxy to reach an HTTPS origin can expose preemptive origin credentials because NettyRequestFactory and NettyRequestSender.sendRequestWithNewChannel attach Authorization to the plaintext CONNECT request before the TLS tunnel exists. Basic or Digest credentials and per-connection NTLM, Kerberos, or SPNEGO tokens intended for the origin are therefore visible to the proxy and to observers on the client-to-proxy hop. The tunneled request still receives origin Authorization after the tunnel is established, while Proxy-Authorization remains on CONNECT for its intended proxy recipient. This issue is fixed in versions 2.16.1 and 3.0.12.
Quoted source text, attributed separately from HOL analysis.