CVE-2026-107282: AsyncHttpClient: Replay to a different host sends the original host request and credentials to the new host
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
AsyncHttpClientto a version that resolves this vulnerability.Fixed in 3.0.13 - Upgrade
Upgrade
AsyncHttpClientto a version that resolves this vulnerability.Fixed in 2.16.1
Event History
Frequently Asked Questions
Which deployments should be prioritized for remediation?
Java applications using AsyncHttpClient versions earlier than 3.0.13 or 2.16.1 should be prioritized, particularly if they use documented ResponseFilter failover or retry paths that can replay requests across hosts.
What data can be exposed when the issue is triggered?
A replay destination can receive the original host's request path, Host header, Authorization credentials, or plaintext request. The flawed replay handling can also affect connection-pool selection, CONNECT handling, realm selection, and TLS setup.
What should teams do if they identify an affected version?
Upgrade AsyncHttpClient to 3.0.13 or 2.16.1. The provided data identifies these versions as containing the fix.
How can teams determine whether their application may exercise the vulnerable path?
Review AsyncHttpClient usage for ResponseFilter implementations that perform failover or retries and can cause a request to be replayed to a different host. Those documented paths can trigger the issue.