# CVE-2026-107282: AsyncHttpClient: Replay to a different host sends the original host request and credentials to the new host

> Attackers can intercept sensitive credentials and request data when cross-host replays incorrectly target the original host's context, affecting Java applications using AsyncHttpClient.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Oct 2026
- **Updated:** 10 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107282, ECHO-6e4c-a2b2-3885, GHSA-jmqq-x5g9-9p2w, MINI-7cgc-w56m-2ww4, MINI-rg5m-vgf5-8gg5, MINI-wmh2-w729-gc6h, MINI-xj9r-m682-mqpr, ROOT-APP-MAVEN-CVE-2026-107282, UBUNTU-CVE-2026-107282

## What is CVE-2026-107282?

CVE-2026-107282 is a critical vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, 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. Prior to 3.0.13  and 2.16.1, cross-host request replay updates the current request but leaves the target request and related proxy context pointing at the original origin. Connection-pool selection, CONNECT handling, realm selection, and TLS setup can consequently send the original host's path, Host header, Authorization credentials, or plaintext request to the replay destination. Documented ResponseFilter failover and retry paths can trigger the replay. This issue is fixed in versions 3.0.13 and 2.16.1.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-441 (Unintended Proxy or Intermediary), CWE-319 (Cleartext Transmission of Sensitive Information)

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

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.0.0 | 2.16.1 |
| `org.asynchttpclient:async-http-client` | Maven | From 2.0.0 | 2.16.1 |
| `org.asynchttpclient:async-http-client` | Maven | From 3.0.0 | 3.0.13 |
| `org.asynchttpclient:async-http-client` | Maven | From 3.0.0 | 3.0.13 |

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

Upgrade org.asynchttpclient:async-http-client to a fixed version for your release line: 2.16.1 or 3.0.13.

## Is CVE-2026-107282 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107282 is a critical vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107282 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.asynchttpclient:async-http-client (Maven): affected from 2.0.0; fixed in 2.16.1
- org.asynchttpclient:async-http-client (Maven): affected from 2.0.0; fixed in 2.16.1
- org.asynchttpclient:async-http-client (Maven): affected from 3.0.0; fixed in 3.0.13
- org.asynchttpclient:async-http-client (Maven): affected from 3.0.0; fixed in 3.0.13

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-107282/ (Markdown: https://insights.sbomify.com/CVE-2026-107282/index.md)
```

## Sources

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

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