CVE-2026-85717: AsyncHttpClient async-http-client · Information Exposure
Affects AsyncHttpClient async-http-clientSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium : upgrade to 3.0.12 or 2.16.1 when convenient.
Data as of 1 Nov 2026, 22:58 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.0.12, 2.16.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 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 1 Nov 2026.
What to do
Upgrade async-http-client and org.asynchttpclient/async-http-client to 3.0.12 or 2.16.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AsyncHttpClientasync-http-client | Affected
| Fixed in
|
| AsyncHttpClientasync-http-client | Affected
| Fixed in
|
Mavenorg.asynchttpclient/async-http-clientpkg:maven/org.asynchttpclient/async-http-clientOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade AsyncHttpClient to version 2.16.1 or later, or 3.0.12 or later, where this issue is fixed. No other mitigation is required as the fix is official and addresses the credential exposure.
Description
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.14.5 to 2.16.0 and from 3.0.9 to 3.0.11, a client configured with a client-wide Realm and redirect following can disclose credentials after a cross-origin redirect because the Interceptors authentication path falls back to the client configuration after redirect handling clears the per-exchange realm. If the attacker-controlled target returns 401, the client can send Basic or Digest credentials or a Negotiate or NTLM token to that origin. Per-request realms are stripped correctly, and this issue is a residual bypass of the earlier cross-origin credential-stripping fixes. This issue is fixed in versions 2.16.1 and 3.0.12.
References
- github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-f8m2-889x-vw4x (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/pull/2224 (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/commit/43db7bba81430cbd61ec2dc2c7be464e0ff6a0ff (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/commit/b66757bec34def2e9867bb2b77bd848b1112abb4 (opens in a new tab)