CVE-2026-107232: AsyncHttpClient async-http-client · Cleartext Transmission
Affects AsyncHttpClient async-http-clientSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 3.0.12 or 2.16.1 soon.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% 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:L/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 21 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 3.0.12 or later on the 3.x branch, or 2.16.1 or later on the 2.x branch, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
Description
AsyncHttpClient versions prior to 3.0.12 on the 3.x branch and 2.16.1 on the 2.x branch have a vulnerability where sensitive credentials can be transmitted in cleartext over a proxy connection. This occurs because the client incorrectly infers proxy tunnel status, allowing authorization credentials to be sent without encryption after a proxy rejects a CONNECT request. The issue is fixed in versions 3.0.12 and 2.16.1.
References
- github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-v9f2-7rw2-gr2x (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/commit/3a625cb892233c0a6653ac68823a25ffbc80f393 (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/commit/a87e7b8c81a6f66a4ce23cd43097fbadd1c788ea (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)