AsyncHttpClient (AHC) library's CookieStore replaces explicitly defined Cookies

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 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 · score source

EPSS

• CVE-2024-53990: 0.72% estimated exploitation activity in the next 30 days; percentile 54.03 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details This issue is described without security warnings here: https://github.com/AsyncHttpClient/async-http-client/issues/1964 A PR to fix this issue has been made: https://github.com/AsyncHttpClient/async-http-client/pull/2033 PoC 1. Add an auth Cookie to the CookieStore - This is identical to receiving an HTTP response that uses Set-Cookie, as shown in issue #1964 above. 2. Handle a different user's request where the same Cookie is provided as a passthrough, like a JWT, and attempt to use it by explicitly providing it. 3. Observe that the user's cookie in step 2 is passed as the Cookie in step 1. Impact This is generally going to be a problem for…

Published by the source

2 Dec 2024, 20:04 UTC

Last modified by the source

18 Dec 2024, 15:56 UTC

Source last checked

26 Oct 2026, 16:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mfj5-cf8g-g2fv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-53990

Advisory: AsyncHttpClient (AHC) library's `CookieStore` replaces explicitly defined `Cookie`s
IDs: CVE-2024-53990, GHSA-mfj5-cf8g-g2fv
Record: https://patchnext.com/advisories/cve-2024-53990 (revision 1, source checked 26 Oct 2026, 16:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.asynchttpclient:async-http-client 3.0.1, 2.12.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.asynchttpclient:async-http-client: affected >= 2.1.0, < 2.12.4; >= 3.0.0.Beta1, < 3.0.1; fixed in 2.12.4, 3.0.1

## Suggested inspection (read-only)
- Maven org.asynchttpclient:async-http-client: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.asynchttpclient:async-http-client.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mfj5-cf8g-g2fv (GitHub-reviewed advisory GHSA-mfj5-cf8g-g2fv lists affected ranges: Maven org.asynchttpclient:async-http-client >=2.1.0 =3.0.0.Beta1 <3.0.1)

Commands are suggestions: review each one before running it.