Threadlinqs IntelligenceStart free

Vendor1 product tracked

AsyncHttpClient vulnerabilities & exploitation

As of 2026-11-19, Threadlinqs tracks 10 AsyncHttpClient CVEs, 0 in the CISA Known Exploited Vulnerabilities catalog, linked to 0 tracked threat campaigns.

CVEs
10Since 2026
CISA KEV
00% of CVEs
Critical
1CVSS v3 9.0+
Avg CVSS
7/10Max 9.4
Threats
0None linked yet
Actors
0None attributed

Data as of:

Exploitation timeline

Threadlinqs has recorded 10 AsyncHttpClient CVEs published between and . The busiest month was 2026-10 (10 new CVEs). None of them is listed in CISA KEV yet.

Most exploited vulnerabilities

Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 10 of 10 tracked AsyncHttpClient CVEs.

Products affected

Threadlinqs normalises CPE and CNA product records across all 10 CVEs; 1 distinct AsyncHttpClient product is affected. The most frequently affected:

  • async-http-client 10 CVEs

Threat activity

No tracked threat campaign references AsyncHttpClient products or CVEs yet. Vulnerability records are still monitored for exploitation and linked as campaigns are ingested.

How to prioritise AsyncHttpClient patching

This order follows the data Threadlinqs holds for AsyncHttpClient, not a generic severity checklist:

  • No AsyncHttpClient CVE is in CISA KEV yet, so rank by exploit probability instead.
  • Outside KEV, the highest EPSS scores are CVE-2026-107279 (0.4%), CVE-2026-107283 (0.3%), CVE-2026-107280 (0.3%).
  • 1 CVE scores Critical and 5 High on CVSS v3 (maximum 9.4, average 7); sequence these after KEV and high-EPSS items.

About this data

Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-11-19 and refresh daily.