ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-107282

AsyncHttpClient: Replay to a different host sends the original host request and credentials to the new host

Published Oct 8, 2026 · catalog updated Oct 8, 2026 · AsyncHttpClient: Replay to a

Check if you run it

No confirmed exploitation is on record for CVE-2026-107282. EPSS is 0.19%. Act only if a listed version of AsyncHttpClient: Replay to a is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (AsyncHttpClient: Replay to a).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.19%
Remediation
Advisory link
Affected products
Maven org.asynchttpclient:async-http-client

### Impact When a request is replayed onto a different host, the client updates only the current request and leaves the target request pointing at the original host. Four consumers read that stale value, and each one sends the first host's request, credentials, or both to the second host. A replay happens through documented, ordinary features: a that returns a different request, which is the supported failover pattern, and the IOException retry path. The attacker does not need to induce the replay; an application that uses failover produces it by design. * The socket to host B is filed in the connection pool under host A's key. A later request the application addresses to A is served over the connection to B, and A's header goes to B. * Over a CONNECT tunnel, the client tunnels to B and negotiates TLS with B correctly, then writes A's request into that tunnel. B receives A's path, A's , and A's . TLS does not protect against this, because the handshake really is with B, so no certificate mismatch occurs. * The replay reuses the original realm, so A's credentials are regenerated onto a replay request that carries no realm of its own. The cross-origin redirect path strips realms for exactly this reason; the replay path never did. * The stale value also decides whether TLS is used at all. When the original request was and the replay is , no SSL handler is installed and the replayed request, credentials included, is written in cleartext. ### Affected versions * 3.x: up to and including 3.0.12 * 2.x: up to and including 2.16.0 Both lines are affected identically. This is long-standing behaviour, not a recent regression. ### Patches Fixed in 3.0.13 on the 3.x line and in 2.16.1 on the 2.x line. The target request now moves when a request is replayed, and the proxy moves with it: the proxy is part of the connection pool key, so correcting only the host would convert a harmless pool miss into a hit and route a proxied connection to a direct request. ### Workarounds Do not u

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Maven org.asynchttpclient:async-http-client2.0.0 → 2.16.1
  • Maven org.asynchttpclient:async-http-client3.0.0 → 3.0.13

How to fix CVE-2026-107282

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-107282. EPSS is 0.19%. Act only if a listed version of AsyncHttpClient: Replay to a is installed.

Which versions are affected?

Compare what you have installed with 2.0.0 → 2.16.1, 3.0.0 → 3.0.13. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-319: Cleartext Transmission of Sensitive Information; CWE-441; CWE-522: Insufficiently Protected Credentials. EPSS 0.19%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 8, 2026 · GitHub Advisory Database

    Detected

    ### Impact When a request is replayed onto a different host, the client updates only the current request and leaves the target request pointing at the original host. Four consumers read that stale value, and each one sends the first host's request, credentials, or both to the second host. A replay happens through documented, ordinary features: a that returns a different request, which is the suppo

  2. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 3.0.13; org.asynchttpclient:async-http-client fixed in 2.16.1

  3. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 3.0.13

  4. Oct 8, 2026 · GitHub Advisory Database

    Fix available

    org.asynchttpclient:async-http-client fixed in 2.16.1

  5. Oct 8, 2026 · GitHub Advisory Database

    Updated

    ### Impact When a request is replayed onto a different host, the client updates only the current request and leaves the target request pointing at the original host. Four consumers read that stale value, and each one sends the first host's request, credentials, or both to the second host. A replay happens through documented, ordinary features: a that returns a different request, which is the suppo

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.