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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.4 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N · score source

EPSS

• CVE-2026-107282: 0.19% estimated exploitation activity in the next 30 days; percentile 8.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 ResponseFilter 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 Authorization 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 Host, and A's Authorization. TLS does not protect against this, because the…

Published by the source

8 Oct 2026, 16:30 UTC

Last modified by the source

8 Oct 2026, 16:45 UTC

Source last checked

26 Oct 2026, 16:58 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jmqq-x5g9-9p2w

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jmqq-x5g9-9p2w

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-107282

Advisory: AsyncHttpClient: Replay to a different host sends the original host request and credentials to the new host
IDs: CVE-2026-107282, GHSA-jmqq-x5g9-9p2w
Record: https://patchnext.com/advisories/cve-2026-107282 (revision 3, source checked 26 Oct 2026, 16:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.asynchttpclient:async-http-client 3.0.13, 2.16.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.asynchttpclient:async-http-client: affected >= 3.0.0, <= 3.0.12; >= 2.0.0, <= 2.16.0; fixed in 2.16.1, 3.0.13

## Suggested inspection (read-only)
- Maven org.asynchttpclient:async-http-client: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.asynchttpclient:async-http-client.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jmqq-x5g9-9p2w (OSV record GHSA-jmqq-x5g9-9p2w lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.0.0 <2.16.1 (fixed))
- Verified: https://github.com/advisories/GHSA-jmqq-x5g9-9p2w (GitHub-reviewed advisory GHSA-jmqq-x5g9-9p2w lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.0 =2.0.0 <=2.16.0)

Commands are suggestions: review each one before running it.