Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-85717 medium CVSS 6.8

Information Disclosure in org.asynchttpclient:async-http-client (CVE-2026-85717)

Summary

Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-85717). Confidential information can be exposed externally. Mitigation: upgrade to 3.0.12 or later.

Original description

The description as published by the source.

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 that the redirect already cleared, rather than being re-derived from the client configuration.

Workarounds

Set the Realm on the individual request instead of on the client configuration. A per-request realm is stripped correctly on a cross-origin redirect while still authenticating same-origin, so this is a complete workaround with no loss of function. Turning off follow-redirects also avoids it. Note that setStripAuthorizationOnRedirect(true) is not a workaround: it forces…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-85717 has been found in org.asynchttpclient:async-http-client.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade org.asynchttpclient:async-http-client to 3.0.12 or later.
If unsure, ask your IT team or search "org.asynchttpclient:async-http-client CVE-2026-85717" on the vendor's site.

CVE-2026-85717 (org.asynchttpclient:async-http-client) — CWE-200 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.0.12 — apply immediately
Workaround: Set the Realm on the individual request instead of on the client configuration.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in org.asynchttpclient:async-http-client.

📍 Affected scope

Check the vendor advisory for the affected versions of org.asynchttpclient:async-http-client.

🔥 Severity

Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.0.12.

🛡️ Workaround

Workaround: Set the Realm on the individual request instead of on the client configuration.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.asynchttpclient:async-http-client を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply temporary workaround mitigate 
    Set the Realm on the individual request instead of on the client configuration.

    パッチが適用されるまでの応急処置として、Set the Realm on the individual request instead of on the client configuration. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade org.asynchttpclient:async-http-client to 3.0.12

    ステージング環境で 3.0.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.asynchttpclient:async-http-client
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.16.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details