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

> Attackers can hijack sessions in shared AsyncHttpClient instances because the cookie store overrides explicit headers, bypassing previous fixes.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107228, GHSA-2jwh-9rmr-j4xf, MINI-5jh9-5wp4-h92q, MINI-w782-qpp6-q395, UBUNTU-CVE-2026-107228

## What is CVE-2026-107228?

CVE-2026-107228 is a medium-severity authentication bypass vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.1.0 until 3.0.14, the enabled-by-default cookie store replaces a Cookie header explicitly supplied through setHeader or addHeader whenever the store contributes any cookie for the origin. In a shared client, stored cookies originating from one user can replace a different user's request cookie, causing the request to execute under the wrong session. This bypasses the earlier CVE-2024-53990 remediation, which covered cookies supplied through addCookie but not a directly supplied header. This issue is fixed in version 3.0.14.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-107228?

4 open source packages ship an affected version, including org.asynchttpclient:async-http-client.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.asynchttpclient:async-http-client` | Maven | From 2.1.0 to 2.16.1 | None |
| `org.asynchttpclient:async-http-client` | Maven | From 2.1.0 to 2.16.1 | None |
| `org.asynchttpclient:async-http-client` | Maven | From 3.0.0 | 3.0.14 |
| `org.asynchttpclient:async-http-client` | Maven | From 3.0.0 | 3.0.14 |

## How do I fix CVE-2026-107228?

Upgrade org.asynchttpclient:async-http-client to 3.0.14 or later.

## Is CVE-2026-107228 being exploited?

There is no known exploitation of CVE-2026-107228 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107228 and fix it if it is affected.

What it is: CVE-2026-107228 is a medium-severity authentication bypass vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107228 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.asynchttpclient:async-http-client (Maven): affected from 2.1.0 up to 2.16.1; no fix listed
- org.asynchttpclient:async-http-client (Maven): affected from 2.1.0 up to 2.16.1; no fix listed
- org.asynchttpclient:async-http-client (Maven): affected from 3.0.0; fixed in 3.0.14
- org.asynchttpclient:async-http-client (Maven): affected from 3.0.0; fixed in 3.0.14

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107228/ (Markdown: https://insights.sbomify.com/CVE-2026-107228/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107228
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107228
- OSV: https://osv.dev/vulnerability/CVE-2026-107228

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107228/
Summaries are generated and may contain mistakes; the official description above is the record.