CVE-2026-107285: AsyncHttpClient async-http-client · Cleartext Transmission
Affects AsyncHttpClient async-http-clientSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 3.0.12 or 2.16.1 when convenient.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% 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:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 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 24 Oct 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 3.0.12 or later, or 2.16.1 or later, where this issue is fixed. No other mitigation is required as the fix is officially available.
Description
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, a proxied ws request is carried through CONNECT, but NettyRequestFactory.newNettyRequest and requestUri decide whether to attach proxy authentication and an absolute-form target only from whether the URI is secure. Because ws is not marked secure, the tunneled WebSocket upgrade sent to the origin includes the proxy's Proxy-Authorization value. Basic credentials are directly recoverable and Digest responses can be replayed or cracked offline. This issue is fixed in versions 3.0.12 and 2.16.1.
References
- github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-3wp9-xfwm-rjjf (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/commit/6e9cb75a9b7259353f983fc90ca28b1da3742e18 (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/commit/c4feab0f7f86d61505a48e40d383c8a375a22e18 (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-2.16.1 (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-3.0.12 (opens in a new tab)