# 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.

**Data as of:** 2026-11-19

## Exploitation timeline

Threadlinqs has recorded 10 AsyncHttpClient CVEs published between 2026-10-15 and 2026-10-15. 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.

- [CVE-2026-107279](https://intel.threadlinqs.com/cve/CVE-2026-107279) — HIGH 8.8 · EPSS 0.4% · 2026-10-07
- [CVE-2026-107283](https://intel.threadlinqs.com/cve/CVE-2026-107283) — LOW 3.7 · EPSS 0.3% · 2026-10-07
- [CVE-2026-107280](https://intel.threadlinqs.com/cve/CVE-2026-107280) — MEDIUM 6.9 · EPSS 0.3% · 2026-10-07
- [CVE-2026-107231](https://intel.threadlinqs.com/cve/CVE-2026-107231) — HIGH 8.7 · EPSS 0.2% · 2026-10-07
- [CVE-2026-107232](https://intel.threadlinqs.com/cve/CVE-2026-107232) — HIGH 7.5 · EPSS 0.2% · 2026-10-07
- [CVE-2026-107285](https://intel.threadlinqs.com/cve/CVE-2026-107285) — MEDIUM 5.9 · EPSS 0.2% · 2026-10-07
- [CVE-2026-107282](https://intel.threadlinqs.com/cve/CVE-2026-107282) — CRITICAL 9.4 · EPSS 0.2% · 2026-10-07
- [CVE-2026-107230](https://intel.threadlinqs.com/cve/CVE-2026-107230) — HIGH 7.4 · EPSS 0.2% · 2026-10-07
- [CVE-2026-107281](https://intel.threadlinqs.com/cve/CVE-2026-107281) — HIGH 7.6 · EPSS 0.2% · 2026-10-07
- [CVE-2026-107284](https://intel.threadlinqs.com/cve/CVE-2026-107284) — LOW 3.7 · EPSS 0.1% · 2026-10-07

## 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](https://intel.threadlinqs.com/cve/CVE-2026-107279) (0.4%), [CVE-2026-107283](https://intel.threadlinqs.com/cve/CVE-2026-107283) (0.3%), [CVE-2026-107280](https://intel.threadlinqs.com/cve/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.

Canonical: https://intel.threadlinqs.com/vendors/asynchttpclient
All vendors: https://intel.threadlinqs.com/vendors
Full detection coverage and IOCs for threats exploiting AsyncHttpClient products unlock per threat with TL Creds (https://threadlinqs.com/tl-creds); the Threadlinqs MCP server (Purple) serves them to AI agents: https://intel.threadlinqs.com/mcp
