ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-107228

AsyncHttpClient CookieStore Silently Overrides Caller's Explicit Cookie Header via setHeader (Bypass of CVE-2024-53990 Fix)

Published Oct 8, 2026 · catalog updated Oct 8, 2026 · AsyncHttpClient CookieStore Silently Overrides

Check if you run it

No confirmed exploitation is on record for CVE-2026-107228. EPSS is 0.30%. Act only if a listed version of AsyncHttpClient CookieStore Silently Overrides is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (AsyncHttpClient CookieStore Silently Overrides).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.30%
Remediation
Advisory link
Affected products
Maven org.asynchttpclient:async-http-client

### Impact With the cookie store enabled, which is the default, a header that the caller sets on a request with or is thrown away whenever the store holds any cookie for the request's origin: the request's cookie list is written into that header afterwards and replaces it. CVE-2024-53990 fixed the same problem for cookies added with , but that fix works on the cookie list, and a header set directly never reaches it. This is not limited to a cookie of the same name. A store cookie of any name erases the caller's header, so a request meant to carry the caller's session cookie goes out with only the store's cookies, and where the store has a cookie of the caller's name, the store's value is sent instead. It matters most where one client acts for several users. An application that puts each user's session on the request itself, and shares one client and its default cookie store, sends one user's request with a session cookie the store took from a response to another user. The request runs as that other user, so a user of such an application can have their request served under someone else's session, or someone else's under theirs. ### Affected versions * 3.x: up to and including 3.0.13 * 2.x: from 2.1.0 up to and including 2.16.1 ### Patches Fixed in 3.0.14. The store's cookies are added to a caller's header instead of replacing it, and where both name the same cookie the caller's is kept. The caller's text is kept as written, and several headers are folded into one, as RFC 6265 Section 5.4 requires. The 2.x line is end of life and will not receive a fix. Upgrade to 3.0.14. ### Workarounds Where requests carry per-user cookies, use a separate client per user, or disable the cookie store with . ### References Incomplete fix of CVE-2024-53990 (GHSA-mfj5-cf8g-g2fv). Reported by @1diot9. ### Attribution AI-assisted tools were used to support discovery and analysis.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Maven org.asynchttpclient:async-http-client2.1.0 → 2.16.1
  • Maven org.asynchttpclient:async-http-client2.1.0, 2.1.1, 2.1.2
  • Maven org.asynchttpclient:async-http-client3.0.0 → 3.0.14

How to fix CVE-2026-107228

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-107228. EPSS is 0.30%. Act only if a listed version of AsyncHttpClient CookieStore Silently Overrides is installed.

Which versions are affected?

Compare what you have installed with 2.1.0 → 2.16.1, 2.1.0, 2.1.1, 2.1.2, 3.0.0 → 3.0.14. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-287: Improper Authentication. EPSS 0.30%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 8, 2026 · Catalog

    Detected

    ### Impact With the cookie store enabled, which is the default, a header that the caller sets on a request with or is thrown away whenever the store holds any cookie for the request's origin: the request's cookie list is written into that header afterwards and replaces it. CVE-2024-53990 fixed the same problem for cookies added with , but that fix works on the cookie list, and a header set directl

  2. Oct 8, 2026 · Catalog

    Fix available

    Maven org.asynchttpclient:async-http-client 3.0.0 → 3.0.14

  3. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 3.0.14

  4. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 3.0.14

  5. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 2.16.1

  6. Oct 8, 2026 · Catalog

    Updated

    ### Impact With the cookie store enabled, which is the default, a header that the caller sets on a request with or is thrown away whenever the store holds any cookie for the request's origin: the request's cookie list is written into that header afterwards and replaces it. CVE-2024-53990 fixed the same problem for cookies added with , but that fix works on the cookie list, and a header set directl

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.