# CVE-2026-107285: AsyncHttpClient: WebSocket proxy credentials sent to the origin server over a CONNECT tunnel

> AsyncHttpClient leaks proxy credentials to origin servers during WebSocket connections, allowing attackers to recover or replay authentication data.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A: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:** 8 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-107285, ECHO-d74c-6231-875e, GHSA-3wp9-xfwm-rjjf, MINI-4rvw-jj9j-cccm, MINI-phmx-4gpx-c53x, MINI-q6ff-r5qp-pr57, MINI-q7qc-c49h-8fhp, UBUNTU-CVE-2026-107285

## What is CVE-2026-107285?

CVE-2026-107285 is a medium-severity 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.12 and 2.16.1, a proxied ws request is carried through CONNECT, but NettyRequestFactory.newNettyRequest and requestUri decide whether to attach proxy authentication and an absolute-form target only from whether the URI is secure. Because ws is not marked secure, the tunneled WebSocket upgrade sent to the origin includes the proxy's Proxy-Authorization value. Basic credentials are directly recoverable and Digest responses can be replayed or cracked offline. This issue is fixed in versions 3.0.12 and 2.16.1.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-319 (Cleartext Transmission of Sensitive Information)

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

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.12 |
| `org.asynchttpclient:async-http-client` | Maven | From 3.0.0 | 3.0.12 |

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

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

## Is CVE-2026-107285 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107285 is a medium-severity 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-107285 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.12
- org.asynchttpclient:async-http-client (Maven): affected from 3.0.0; fixed in 3.0.12

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

## Sources

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

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