Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-107283)
Summary
Vulnerability in org.asynchttpclient:async-http-client (CVE-2026-107283). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.0.12 or later.
Original description
The description as published by the source.
Impact
The client nonce used in HTTP Digest authentication was generated from ThreadLocalRandom, a fast but non-cryptographic pseudorandom number generator. RFC 7616 section 3.3 requires the cnonce to be unpredictable, since it is part of what protects the Digest exchange against chosen-plaintext and precomputation attacks on the credentials. An attacker able to observe or influence enough of the generator's output could reduce the unpredictability the protocol depends on. NTLM (and, on the 3.x line, SCRAM) in this client already use SecureRandom for their own nonces; Digest did not.
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 cnonce is now generated with SecureRandom, matching the other authentication schemes in the client.
Workarounds
None available from application code.
Details
Realm.Builder's cnonce generation seeded its bytes from ThreadLocalRandom.current() rather than a SecureRandom instance.
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-107283 has been found in org.asynchttpclient:async-http-client.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/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-107283" on the vendor's site.
CVE-2026-107283 (org.asynchttpclient:async-http-client) — CWE-338 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.0.12 — apply immediately
Workaround: None available from application code.
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-338) exists in org.asynchttpclient:async-http-client.
Check the vendor advisory for the affected versions of org.asynchttpclient:async-http-client.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 3.0.12.
Workaround: None available from application code.
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
None available from application code.パッチが適用されるまでの応急処置として、None available from application code. を実施。回避策の副作用 (機能低下) を確認した上で。
-
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
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