Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-107231

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

Summary

Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-107231). Risk of unauthorized operations or information disclosure. Exploitable via Authorization header. Mitigation: upgrade to 3.0.13 or later.

Original description

The description as published by the source.

Impact

A Digest challenge that does not yield a usable nonce is treated as a Basic challenge. The client then answers it with Authorization: Basic, which carries the username and password base64 encoded and so recoverable by anyone who sees the request.

Any of these is enough, sent by whoever writes the 401 or 407:

WWW-Authenticate: Digest realm="protected"
WWW-Authenticate: Digest realm="protected", nonce=""

The challenge announces itself as Digest, so it passes the check that would otherwise reject a non-Digest challenge for a Digest realm. It then fails to produce a nonce, and the absence of a nonce is what selected Basic. A server offering plain Basic to a Digest realm gets nothing, so labelling the challenge Digest and leaving the nonce out is what makes the difference.

This is reachable by anyone who can write the challenge: a malicious or compromised origin, a proxy, or an attacker on a plaintext hop. Digest exists precisely to keep the password off those hops. A server that stores only HA1, and anyone impersonating the real origin, does not otherwise learn the password itself, so the disclosure enables reuse against other services.

Both the target and the proxy paths are affected, through parseWWWAuthenticateHeader and parseProxyAuthenticateHeader.

Affected versions

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

This is long-standing behaviour on both lines, not a recent regression. On 3.0.12 there is one additional…

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-107231 has been found in org.asynchttpclient:async-http-client.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.asynchttpclient:async-http-client to 3.0.13 or later.
If unsure, ask your IT team or search "org.asynchttpclient:async-http-client CVE-2026-107231" on the vendor's site.

CVE-2026-107231 (org.asynchttpclient:async-http-client) — CWE-319
Attack surface: Authorization header / Basic / parseWWWAuthenticateHeader / parseProxyAuthenticateHeader
Patched: 3.0.13 — apply immediately
Workaround: No configuration prevents this.
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. Attackers reach the vulnerable code path via Authorization header.

📍 Affected scope

Check the vendor advisory for the affected versions of org.asynchttpclient:async-http-client. Attack surface: Authorization header / Basic / parseWWWAuthenticateHeader / parseProxyAuthenticateHeader.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.0.13.

🛡️ Workaround

Workaround: No configuration prevents this.

🔍 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 
    No configuration prevents this.

    パッチが適用されるまでの応急処置として、No configuration prevents this. を実施。回避策の副作用 (機能低下) を確認した上で。

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

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

  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":"2.0.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