Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-85720 medium CVSS 5.9

Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-85720)

Summary

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

Original description

The description as published by the source.

Impact

When a request uses an HTTP proxy to reach an HTTPS origin, the client opens the tunnel with a plaintext CONNECT sent to the proxy before any TLS exists. On affected versions the origin's preemptive credentials were added to that CONNECT. A Basic realm sent Authorization: Basic base64(user:pass) to the proxy in the clear, and NTLM, SPNEGO or Kerberos realms sent their token. The proxy, and anyone who can read the client to proxy hop, saw credentials that were meant only for the origin.

Affected versions

  • 3.x: up to and including 3.0.11
  • 2.x: up to and including 2.16.0

Patches

Fixed in 3.0.12 on the 3.x line and in 2.16.1 on the 2.x line. The origin Basic or Digest Authorization is no longer put on the CONNECT; it is added to the tunnelled request once the tunnel is up. The per-connection NTLM, Kerberos and SPNEGO token is likewise no longer attached on the tunnel path; it never reached the origin there in any case, and the challenge flow still negotiates it inside the tunnel.

Workarounds

Do not use preemptive origin authentication together with an HTTP proxy, or reach the origin without a CONNECT proxy.

Details

NettyRequestFactory added the origin Authorization to every request it built, including the CONNECT, and NettyRequestSender did the same for the per-connection NTLM or SPNEGO token in sendRequestWithNewChannel. Both now skip the CONNECT.

Note that 3.0.12 is itself affected by a separate issue, GHSA-rqf5-2wxv-rjf4, where a Digest chal…

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-85720 has been found in org.asynchttpclient:async-http-client.
Confidential information can be exposed externally. CVSS score: 5.9/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-85720" on the vendor's site.

CVE-2026-85720 (org.asynchttpclient:async-http-client) — CWE-319 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.0.12 — apply immediately
Workaround: Do not use preemptive origin authentication together with an HTTP proxy, or reach the origin without a CONNECT proxy.
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

A vulnerability (CWE-319) 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 5.9/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.0.12.

🛡️ Workaround

Workaround: Do not use preemptive origin authentication together with an HTTP proxy, or reach the origin without a CONNECT proxy.

🔍 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 
    Do not use preemptive origin authentication together with an HTTP proxy, or reach the origin without a CONNECT proxy.

    パッチが適用されるまでの応急処置として、Do not use preemptive origin authentication together with an HTTP proxy, or reach the origin without a CONNECT proxy. を実施。回避策の副作用 (機能低下) を確認した上で。

  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