Skip to main content
VulnerabilityPublished

CVE-2026-107229: AsyncHttpClient async-http-client · Session Fixation

Affects AsyncHttpClient async-http-clientSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.0 Medium : upgrade to 3.0.14 when convenient.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% 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:N/UI:N/S:C/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
AsyncHttpClientasync-http-clientAffected
  • >=3.0.11 <3.0.14
  • >=2.16.0 <=2.16.1
Fixed in
  • 3.0.14
Mavenorg.asynchttpclient/async-http-clientpkg:maven/org.asynchttpclient/async-http-clientOther threatsAffected
  • >=3.0.11 <3.0.14
  • >=2.16.0 <=2.16.1
Fixed in
  • 3.0.14

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 by the vendor advisory.

Description

The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.16.0 until 3.0.14, ThreadSafeCookieStore incompletely validates cookie Domain attributes. Missing private-section and default public-suffix rules, absent A-label normalization, locale-sensitive lowercasing, public-suffix host-only handling, and numeric or IP host checks allow one origin to store a cookie later sent to another origin. Applications sharing one client across trust domains can therefore receive attacker-injected cookies and may be exposed to session fixation. This issue is fixed in version 3.0.14.

References

Community reviews

Loading reviews…