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

Published Oct 7, 2026
·
Updated

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.

Other sources

The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. Prior to 3.0.12 and 2.16.1, Realm.Builder generates the HTTP Digest client nonce with ThreadLocalRandom rather than a cryptographically secure random source. Digest relies on an unpredictable cnonce to resist chosen-plaintext and credential precomputation attacks, so an observer able to infer generator state can reduce the protection of the authentication exchange. This issue is fixed in versions 3.0.12 and 2.16.1.

— MITRE

Affected Software

3 affected componentsFixes available
maven/org.asynchttpclient/async-http-client<3.0.12, <2.16.1
maven/org.asynchttpclient:async-http-client>=2.0.0<=2.16.0
2.16.1
maven/org.asynchttpclient:async-http-client>=3.0.0<=3.0.11
3.0.12

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.asynchttpclient:async-http-client to a version that resolves this vulnerability.

    Fixed in 2.16.1
  2. Upgrade

    Upgrade maven/org.asynchttpclient:async-http-client to a version that resolves this vulnerability.

    Fixed in 3.0.12
  3. Upgrade

    Upgrade AsyncHttpClient to a version that resolves this vulnerability.

    Fixed in 3.0.12
  4. Upgrade

    Upgrade AsyncHttpClient to a version that resolves this vulnerability.

    Fixed in 2.16.1

Event History

Oct 7, 2026
CVE Published
via MITRE·09:24 PM
Data Sourced
via MITRE·09:24 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:17 PM
DescriptionSeverityWeakness
Oct 8, 2026
Advisory Published
via GitHub·04:31 PM
Data Sourced
via GitHub·04:31 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed?

Java applications using AsyncHttpClient versions earlier than 3.0.12 or 2.16.1 are affected when they use HTTP Digest authentication through Realm.Builder. The issue concerns the client nonce generated for Digest authentication exchanges.

2

What does an attacker need to exploit this weakness?

An attacker needs to observe the Digest authentication exchange and be able to infer the state of the ThreadLocalRandom generator used to create the client nonce. This can reduce Digest authentication's resistance to chosen-plaintext and credential precomputation attacks.

3

What is the remediation?

Upgrade AsyncHttpClient to version 3.0.12 or 2.16.1, which replace the non-cryptographic random source used for the Digest client nonce.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203