CVE-2026-107228: AsyncHttpClient async-http-client · Improper Authentication
Affects AsyncHttpClient async-http-clientSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.8 Medium : upgrade to 3.0.14 when convenient.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.0.14
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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.14.
Affected software
| Product | 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.14 or later, where this issue is fixed. No other mitigations are indicated. Patch status is confirmed fixed in 3.0.14.
Description
AsyncHttpClient versions from 2.1.0 up to 2.16.1 and from 3.0.0 up to but not including 3.0.14 have an improper authentication vulnerability. The enabled-by-default cookie store can overwrite explicitly set Cookie headers in HTTP requests, causing requests to execute under the wrong user session. This bypasses previous remediation efforts and can lead to session confusion. The issue is fixed in version 3.0.14.
References
- github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-2jwh-9rmr-j4xf (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/commit/fd9763620725126c1c8bb0af1ceb9a7523099a5f (opens in a new tab)
- github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-3.0.14 (opens in a new tab)