# CVE-2026-107283 — AsyncHttpClient async-http-client

> As of 2026-10-08, CVE-2026-107283 is a LOW-severity vulnerability in AsyncHttpClient async-http-client, CVSS v3.1 3.7, EPSS 0.2% (16.5th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-107283 as of 2026-10-08; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-08

## What is CVE-2026-107283?

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.

The record classifies CVE-2026-107283 under weakness class [CWE-338](https://cwe.mitre.org/data/definitions/338.html). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 43 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 3.7 — LOW (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 16.5% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 2.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-07

## Is CVE-2026-107283 being exploited?

It currently carries a trending score of 34 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [AsyncHttpClient](https://intel.threadlinqs.com/vendors/asynchttpclient): async-http-client

Affected software packages:

- `maven:org.asynchttpclient:async-http-client` — patched in 3.0.12
- `maven:org.asynchttpclient:async-http-client` — patched in 2.16.1

## How to fix CVE-2026-107283

Fixed versions are recorded for 2 packages: maven:org.asynchttpclient:async-http-client 3.0.12, maven:org.asynchttpclient:async-http-client 2.16.1. No vendor patch reference has been recorded for CVE-2026-107283 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-107283

No threat campaign in the Threadlinqs corpus currently references CVE-2026-107283, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/AsyncHttpClient/async-http-client/security/advisories/GHSA-mfj3-87qq-382v)

**Other references**

- [github.com](https://github.com/AsyncHttpClient/async-http-client/commit/dca2d90db87f0144ea893a6858dca13c426d06b6)
- [github.com (e1f5fc88fe211d3f64032c33b91093ba3d5e793d)](https://github.com/AsyncHttpClient/async-http-client/commit/e1f5fc88fe211d3f64032c33b91093ba3d5e793d)
- [github.com (async http client project 2.16)](https://github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-2.16.1)
- [github.com (async http client project 3.0)](https://github.com/AsyncHttpClient/async-http-client/releases/tag/async-http-client-project-3.0.12)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-107283
No Threadlinqs detection currently covers CVE-2026-107283; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
