Skip to content
Fencer Intel
critical 9.2

CVE-2024-53990 json

AsyncHttpClient (AHC) library's `CookieStore` replaces explicitly defined `Cookie`s

published last yr. modified 2mo ago also EUVD-2024-3488 , GHSA-mfj5-cf8g-g2fv

cvss
9.2
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. When making any HTTP request, the automatically enabled and self-managed CookieStore (aka cookie jar) will silently replace explicitly defined Cookies with any that have the same name from the cookie jar. For services that operate with multiple users, this can result in one user's Cookie being used for another user's requests.

Patch / fix

  • maven org.asynchttpclient:async-http-client 2.12.4, 3.0.1
  • asynchttpclient_project async-http-client 3.0.1

Is CVE-2024-53990 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-53990 updated cvss 8.1

async-http-client: AsyncHttpClient (AHC) library's `CookieStore` replaces explicitly defined `Cookie`s

  • Red Hat Fuse 7 org.asynchttpclient/async-http-client org.asynchttpclient/async-http-client Red Hat Integration Camel K 1 org.asynchttpclient/async-http-client org.asynchttpclient/async-http-client
    affected: workaround, no fix planned “Users may bypass this issue by disabling the CookieStore upon client creation: DefaultAsyncHttpClientConfig.Builder clientBuilder = Dsl.config().setCookieStore(null)”
  • Red Hat build of Apache Camel 4.8.3 for Spring Boot
    fixed: vendor fix “Users may bypass this issue by disabling the CookieStore upon client creation: DefaultAsyncHttpClientConfig.Builder clientBuilder = Dsl.config().setCookieStore(null)” RHSA-2025:1078
  • Red Hat build of Apache Camel 4 for Quarkus 3 org.asynchttpclient/async-http-client org.asynchttpclient/async-http-client Red Hat Build of Keycloak org.asynchttpclient/async-http-client org.asynchttpclient/async-http-client Red Hat build of Quarkus org.asynchttpclient/async-http-client org.asynchttpclient/async-http-client Red Hat JBoss Data Grid 7 org.asynchttpclient/async-http-client org.asynchttpclient/async-http-client Red Hat JBoss Enterprise Application Platform 7 async-http-client Red Hat JBoss Enterprise Application Platform 8 async-http-client
    +1 more products
    Red Hat JBoss Enterprise Application Platform Expansion Pack async-http-client
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 4.0 9.2 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA 4.0 9.2 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
maven org.asynchttpclient:async-http-client
>=2.1.0, <2.12.4
>=3.0.0.Beta1, <3.0.1
2.12.4
3.0.1

Affected products

  • AsyncHttpClient async-http-client
  • asynchttpclient_project async-http-client

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.