# CVE-2026-85717: AsyncHttpClient: Client-wide realm credentials re-sent to a cross-origin redirect target

> AsyncHttpClient leaks client-wide credentials to cross-origin redirect targets when configured with a global realm and redirect following.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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:** 17 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** ECHO-7764-b5b5-9fbb, GHSA-f8m2-889x-vw4x, MINI-922h-r7vp-fph3, MINI-g37c-928q-vjx3, MINI-qhhj-xprf-wmpc, MINI-xvjh-6ppq-32hg, UBUNTU-CVE-2026-85717

## What is CVE-2026-85717?

CVE-2026-85717 is a medium-severity vulnerability in AsyncHttpClient async-http-client, published on 17 Sep 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. From 2.14.5 to 2.16.0 and from 3.0.9 to 3.0.11, a client configured with a client-wide Realm and redirect following can disclose credentials after a cross-origin redirect because the Interceptors authentication path falls back to the client configuration after redirect handling clears the per-exchange realm. If the attacker-controlled target returns 401, the client can send Basic or Digest credentials or a Negotiate or NTLM token to that origin. Per-request realms are stripped correctly, and this issue is a residual bypass of the earlier cross-origin credential-stripping fixes. This issue is fixed in versions 2.16.1 and 3.0.12.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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.14.5 | 2.16.1 |
| `org.asynchttpclient:async-http-client` | Maven | From 2.14.5 | 2.16.1 |
| `org.asynchttpclient:async-http-client` | Maven | From 3.0.9 | 3.0.12 |
| `org.asynchttpclient:async-http-client` | Maven | From 3.0.9 | 3.0.12 |

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

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

## Is CVE-2026-85717 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85717 is a medium-severity vulnerability in AsyncHttpClient async-http-client, published on 17 Sep 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-85717 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.asynchttpclient:async-http-client (Maven): affected from 2.14.5; fixed in 2.16.1
- org.asynchttpclient:async-http-client (Maven): affected from 2.14.5; fixed in 2.16.1
- org.asynchttpclient:async-http-client (Maven): affected from 3.0.9; fixed in 3.0.12
- org.asynchttpclient:async-http-client (Maven): affected from 3.0.9; 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-85717/ (Markdown: https://insights.sbomify.com/CVE-2026-85717/index.md)
```

## Sources

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

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