CVE-2026-45300: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in AsyncHttpClient async-http-client
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. Versions on the 2.x branch prior to 2.15.0 and the 3.x branch prior to 3.0.10 leak `Cookie` headers to cross-origin redirect targets. When following a redirect to a different origin, the `propagatedHeaders()` method in `Redirect30xInterceptor.java` strips `Authorization` and `Proxy-Authorization` headers but does not strip the `Cookie` header, causing session cookies and other sensitive cookie values to be sent to attacker-controlled servers. Versions 2.15.0 and 3.0.10 patch the issue.
AI Analysis
Technical Summary
The AsyncHttpClient (AHC) library for Java applications has a vulnerability (CVE-2026-45300) where Cookie headers are leaked to cross-origin redirect targets. Specifically, in versions before 2.15.0 (2.x branch) and 3.0.10 (3.x branch), the method propagating headers during HTTP 30x redirects strips Authorization and Proxy-Authorization headers but does not strip Cookie headers. This results in session cookies and other sensitive cookie values being sent to potentially attacker-controlled servers when following redirects to different origins. The vulnerability is addressed in versions 2.15.0 and 3.0.10.
Potential Impact
An attacker controlling a redirect target can receive sensitive Cookie header information, including session cookies, from an AsyncHttpClient user following a cross-origin redirect. This exposure can lead to session hijacking or unauthorized access to user sessions. The vulnerability does not affect Authorization headers, which are properly stripped, and does not impact availability or integrity.
Mitigation Recommendations
Upgrade AsyncHttpClient to version 2.15.0 or later on the 2.x branch, or version 3.0.10 or later on the 3.x branch. These versions include fixes that prevent Cookie headers from being sent to cross-origin redirect targets. No other mitigation is required as the issue is resolved in these versions.
CVE-2026-45300: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in AsyncHttpClient async-http-client
Description
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. Versions on the 2.x branch prior to 2.15.0 and the 3.x branch prior to 3.0.10 leak `Cookie` headers to cross-origin redirect targets. When following a redirect to a different origin, the `propagatedHeaders()` method in `Redirect30xInterceptor.java` strips `Authorization` and `Proxy-Authorization` headers but does not strip the `Cookie` header, causing session cookies and other sensitive cookie values to be sent to attacker-controlled servers. Versions 2.15.0 and 3.0.10 patch the issue.
CVSS v3.1
Score 7.4high
Affected software
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.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The AsyncHttpClient (AHC) library for Java applications has a vulnerability (CVE-2026-45300) where Cookie headers are leaked to cross-origin redirect targets. Specifically, in versions before 2.15.0 (2.x branch) and 3.0.10 (3.x branch), the method propagating headers during HTTP 30x redirects strips Authorization and Proxy-Authorization headers but does not strip Cookie headers. This results in session cookies and other sensitive cookie values being sent to potentially attacker-controlled servers when following redirects to different origins. The vulnerability is addressed in versions 2.15.0 and 3.0.10.
Potential Impact
An attacker controlling a redirect target can receive sensitive Cookie header information, including session cookies, from an AsyncHttpClient user following a cross-origin redirect. This exposure can lead to session hijacking or unauthorized access to user sessions. The vulnerability does not affect Authorization headers, which are properly stripped, and does not impact availability or integrity.
Mitigation Recommendations
Upgrade AsyncHttpClient to version 2.15.0 or later on the 2.x branch, or version 3.0.10 or later on the 3.x branch. These versions include fixes that prevent Cookie headers from being sent to cross-origin redirect targets. No other mitigation is required as the issue is resolved in these versions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-11T20:14:43.202Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a232f23e29bf47b50ba9e34
Added to database: 06/05/2026, 20:18:43 UTC
Last enriched: 06/13/2026, 09:47:59 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 70
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.