CVE-2026-107282: AsyncHttpClient async-http-client · Cleartext Transmission
Affects AsyncHttpClient async-http-clientSource CVE Database V5
Not known to be exploited · CVSS 9.4 Critical : upgrade to 3.0.13 or 2.16.1 as a priority.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.0.13, 2.16.1
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA: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.13 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.13 or later, or 2.16.1 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Patch status is confirmed fixed in these versions.
Description
CVE-2026-107282 is a critical vulnerability in the AsyncHttpClient (AHC) Java library that allows cleartext transmission of sensitive information. Versions prior to 3.0.13 and 2.16.1 have a flaw where cross-host request replay can cause the original host's sensitive data, including path, Host header, and Authorization credentials, to be sent to an unintended replay destination. This occurs due to improper updating of the target request and proxy context during failover and retry scenarios. The issue is fixed in versions 3.0.13 and 2.16.1.
References
- github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-jmqq-x5g9-9p2w (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/commit/15b254514a411623e5f1d8c99ea79c0f82f8a466 (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/commit/bbc31aed3b044f9f7a126cf689a8c8d7ad2ae1cb (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.13 (opens in a new tab)