CVE-2026-85717: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in AsyncHttpClient async-http-client
AsyncHttpClient versions 2.14.5 to 2.16.0 and 3.0.9 to 3.0.11 have a vulnerability where client-wide credentials can be exposed after a cross-origin redirect. This occurs because the authentication path falls back to client-wide credentials after redirect handling clears the per-request realm, potentially disclosing Basic, Digest, Negotiate, or NTLM credentials to an attacker-controlled origin. The issue is fixed in versions 2.16.1 and 3.0.12.
AI Analysis
Technical Summary
The AsyncHttpClient (AHC) library allows Java applications to execute HTTP requests asynchronously. Versions 2.14.5 through 2.16.0 and 3.0.9 through 3.0.11 contain a vulnerability where a client configured with a client-wide Realm and redirect following can disclose credentials after a cross-origin redirect. This happens because the authentication interceptors fall back to the client-wide configuration after the per-exchange realm is cleared during redirect handling. If the redirected-to server is attacker-controlled and returns a 401 response, the client may send sensitive authentication credentials (Basic, Digest, Negotiate, or NTLM) to that origin. Per-request realms are handled correctly, so this is a residual bypass of previous cross-origin credential-stripping fixes. The vulnerability is resolved in versions 2.16.1 and 3.0.12.
Potential Impact
An attacker controlling a redirect target can cause the client to send sensitive authentication credentials to an unauthorized origin after a cross-origin redirect. This leads to exposure of sensitive information (credentials) without impacting integrity or availability. The CVSS score is 6.8 (medium severity) with high confidentiality impact and no integrity or availability impact.
Mitigation Recommendations
Upgrade AsyncHttpClient to version 2.16.1 or later, or 3.0.12 or later, where this vulnerability is fixed. No other mitigations are specified or required as the fix addresses the root cause.
CVE-2026-85717: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in AsyncHttpClient async-http-client
Description
AsyncHttpClient versions 2.14.5 to 2.16.0 and 3.0.9 to 3.0.11 have a vulnerability where client-wide credentials can be exposed after a cross-origin redirect. This occurs because the authentication path falls back to client-wide credentials after redirect handling clears the per-request realm, potentially disclosing Basic, Digest, Negotiate, or NTLM credentials to an attacker-controlled origin. The issue is fixed in versions 2.16.1 and 3.0.12.
CVSS v3.1
Score 6.8medium
Affected software
AsyncHttpClient
async-http-client
pkg:maven/org.asynchttpclient/async-http-clientRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The AsyncHttpClient (AHC) library allows Java applications to execute HTTP requests asynchronously. Versions 2.14.5 through 2.16.0 and 3.0.9 through 3.0.11 contain a vulnerability where a client configured with a client-wide Realm and redirect following can disclose credentials after a cross-origin redirect. This happens because the authentication interceptors fall back to the client-wide configuration after the per-exchange realm is cleared during redirect handling. If the redirected-to server is attacker-controlled and returns a 401 response, the client may send sensitive authentication credentials (Basic, Digest, Negotiate, or NTLM) to that origin. Per-request realms are handled correctly, so this is a residual bypass of previous cross-origin credential-stripping fixes. The vulnerability is resolved in versions 2.16.1 and 3.0.12.
Potential Impact
An attacker controlling a redirect target can cause the client to send sensitive authentication credentials to an unauthorized origin after a cross-origin redirect. This leads to exposure of sensitive information (credentials) without impacting integrity or availability. The CVSS score is 6.8 (medium severity) with high confidentiality impact and no integrity or availability impact.
Mitigation Recommendations
Upgrade AsyncHttpClient to version 2.16.1 or later, or 3.0.12 or later, where this vulnerability is fixed. No other mitigations are specified or required as the fix addresses the root cause.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-04T14:45:10.648Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aac65c155bf5e2cf5fdf664
Added to database: 09/17/2026, 22:12:17 UTC
Last enriched: 09/17/2026, 22:15:21 UTC
Last updated: 09/18/2026, 00:30:54 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.