Advisory record · GHSA-mfj5-cf8g-g2fv

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

CVSS 9.2 CriticalCriticalEPSS 0.0073 · 54th percentile

Critical, because:

  • CVSS score 9.2: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 2 Dec 2024, 20:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.asynchttpclient:async-http-clientMaven>=2.1.0, <2.12.4 || >=3.0.0.Beta1, <3.0.12.12.4, 3.0.1
Identifiers
GHSA-mfj5-cf8g-g2fv · CVE-2024-53990
Weakness (CWE)
CWE-287
Published
2 Dec 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Maven package org.asynchttpclient:async-http-client, versions from 2.1.0 before 2.12.4 and from 3.0.0.Beta1 before 3.0.1, has a flaw where the automatic cookie store silently replaces explicitly set cookies with same-named cookies from the store. An attacker who can get a cookie into the shared store, such as through a Set-Cookie response, can cause one user's cookie to be sent in another user's requests, which may expose that user's information. Upgrade to 2.12.4 or 3.0.1. Alternatively, disable the cookie store when creating the client.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.2 Critical 4.0 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 (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0073, the 54th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.