Low

AsyncHttpClient: Digest authentication cnonce generated with a non-cryptographic random source

  • Disclosed: 08.10.2026
  • Updated: 11.10.2026 13:20

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Java / Kotlin (Maven) org.asynchttpclient:async-http-client >= 3.0.0, < 3.0.12, >= 2.0.0, < 2.16.1 3.0.12, 2.16.1

References

CVSS score 3.7/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness (CWE)
CWE-338
Platform
Java / Kotlin (Maven)
Package
org.asynchttpclient:async-http-client
Disclosed
08.10.2026
Updated
11.10.2026 13:20

Sources and licenses

OSV / GitHub Advisory Database - GHSA-mfj3-87qq-382v - CC BY 4.0

Vulnerability history: org.asynchttpclient:async-http-client

All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (18) in the archive
Total entries
18
First → latest
10.2018 10.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 2
  • High 6
  • Medium 8
  • Low 2

Disclosures per year

  1. 2018: 1
  2. 2019: 0
  3. 2020: 0
  4. 2021: 0
  5. 2022: 0
  6. 2023: 0
  7. 2024: 1
  8. 2025: 0
  9. 2026: 16
Severity:
  1. High · 7.4 CVE-2026-107230 >= 3.0.0, < 3.0.14, >= 2.0.0, <= 2.16.1 3.0.14
  2. AsyncHttpClient: Digest authentication cnonce generated with a non-cryptographic random source this entry
    Low · 3.7 CVE-2026-107283 >= 3.0.0, < 3.0.12, >= 2.0.0, < 2.16.1 3.0.12, 2.16.1
  3. Critical CVE-2026-107282 >= 3.0.0, < 3.0.13, >= 2.0.0, < 2.16.1 3.0.13, 2.16.1
  4. High CVE-2026-107231 >= 3.0.0.Beta1, < 3.0.13, >= 2.0.0, < 2.16.1 3.0.13, 2.16.1
  5. High · 7.5 CVE-2026-85721 >= 3.0.0, < 3.0.12, >= 2.0.0, < 2.16.1 3.0.12, 2.16.1
  6. High · 7.4 CVE-2026-45300 >= 3.0.0.Beta1, < 3.0.10, >= 2.0.0, < 2.15.0 3.0.10, 2.15.0
  7. Critical CVE-2024-53990 >= 2.1.0, < 2.12.4, >= 3.0.0.Beta1, < 3.0.1 2.12.4, 3.0.1
  8. High · 7.5 CVE-2017-14063 < 2.0.35 2.0.35

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.