Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-107285)
Summary
Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-107285). Confidential information can be exposed externally. Exploitable via Authorization header. Mitigation: upgrade to 3.0.12 or later.
Original description
The description as published by the source.
Impact
When a ws:// request is routed through an HTTP proxy with proxy authentication configured, the client tunnels the connection with an HTTP CONNECT, the same as it does for https://. Once the tunnel is open, the WebSocket upgrade request that follows is sent through the tunnel directly to the origin server, not to the proxy. The proxy-auth gate and the companion request-target selection keyed only on whether the URI was secured, which is false for ws://, so the tunnelled upgrade request incorrectly carried the proxy's Proxy-Authorization header and an absolute-form request target meant for the proxy. Any origin server reached over a proxied ws:// connection, or anyone positioned on the origin side of the wire, could recover the proxy credentials: directly for Basic, or as a replayable and offline-crackable response for Digest.
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 preemptive Proxy-Authorization header and the absolute-form request target are no longer attached to a tunnelled ws:// upgrade; a ws:// request is now treated like wss://.
Workarounds
Do not use proxy authentication together with ws:// requests through an HTTP proxy, or use wss:// instead.
Details
The proxy-auth gate in NettyRequestFactory#newNettyRequest and the sibling branch in requestUri() did not exclude WebSocket URIs, even though the CONNECT-tunnelling check i…
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-107285 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.
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-107285" on the vendor's site.
CVE-2026-107285 (org.asynchttpclient:async-http-client) — CWE-319 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Authorization header
Patched: 3.0.12 — apply immediately
Workaround: Do not use proxy authentication together with ws:// requests through an HTTP proxy, or use wss:// instead.
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.
A vulnerability (CWE-319) exists in org.asynchttpclient:async-http-client. Attackers reach the vulnerable code path via Authorization header without authentication.
Check the vendor advisory for the affected versions of org.asynchttpclient:async-http-client. Attack surface: Authorization header.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 3.0.12.
Workaround: Do not use proxy authentication together with ws:// requests through an HTTP proxy, or use wss:// instead.
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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.asynchttpclient:async-http-client を使っているサービスとバージョンを洗い出す。
-
2Apply temporary workaround mitigate
Do not use proxy authentication together with ws:// requests through an HTTP proxy, or use wss:// instead.パッチが適用されるまでの応急処置として、Do not use proxy authentication together with ws:// requests through an HTTP proxy, or use wss:// instead. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade org.asynchttpclient:async-http-client to 3.0.12ステージング環境で 3.0.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-107285 async-http-client
- Ubuntu UBUNTU-CVE-2026-107285 async-http-client
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com