AsyncHttpClient re-sends client-wide realm credentials to a cross-origin redirect target
CVE-2026-85717GHSA-f8m2-889x-vw4x
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.asynchttpclient:async-http-client 3.0.12, 2.16.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.asynchttpclient:async-http-client
- Affected
- >= 3.0.9, <= 3.0.11>= 2.14.5, <= 2.16.0
- Fixed in
- 2.16.1, 3.0.12
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-f8m2-889x-vw4x lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.9 =2.14.5 <2.16.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-f8m2-889x-vw4x lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.9 =2.14.5 <=2.16.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N
- EPSS
- CVE-2026-85717: 0.53% estimated exploitation activity in the next 30 days; percentile 44.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact A client configured with a client-wide realm (a Realm set on the config builder rather than on an individual request) and following redirects could re-send those credentials to a redirect target on a different origin. The redirect code strips the per-exchange realm, but when the target answered 401 the credentials were re-derived from the client config, handing Basic or Digest credentials, or a Negotiate or NTLM token, to an attacker controlled origin. This is a residual of the earlier cross-origin credential leak advisories, whose strip this bypassed. Affected versions 3.x: 3.0.9 through 3.0.11 2.x: 2.14.5 through 2.16.0 Releases below those floors are covered by the earlier advisories GHSA-cmxv-58fp-fm3g and GHSA-fmxf-pm6p-7xgm: the cross-origin strip that this issue bypasses did not exist yet, so the leak there is the original one rather than this residual. Patches Fixed in 3.0.12 on the 3.x line and in 2.16.1 on the 2.x line. The realm is taken from the per-exchange state…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-f8m2-889x-vw4x
- Revision 1 · created ·
Published from osv record GHSA-f8m2-889x-vw4x
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-85717 Advisory: AsyncHttpClient re-sends client-wide realm credentials to a cross-origin redirect target IDs: CVE-2026-85717, GHSA-f8m2-889x-vw4x Record: https://patchnext.com/advisories/cve-2026-85717 (revision 2, source checked 26 Oct 2026, 16:55 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.8) 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.12, 2.16.1. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.asynchttpclient:async-http-client: affected >= 3.0.9, <= 3.0.11; >= 2.14.5, <= 2.16.0; fixed in 2.16.1, 3.0.12 ## 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-f8m2-889x-vw4x (OSV record GHSA-f8m2-889x-vw4x lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.9 =2.14.5 <2.16.1 (fixed)) - Verified: https://github.com/advisories/GHSA-f8m2-889x-vw4x (GitHub-reviewed advisory GHSA-f8m2-889x-vw4x lists affected ranges: Maven org.asynchttpclient:async-http-client >=3.0.9 =2.14.5 <=2.16.0) Commands are suggestions: review each one before running it.
Loading voting…