Exploitation timeline
Threadlinqs has recorded 8 knowns-dev CVEs published between and . The busiest month was 2026-09 (8 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 8 of 8 tracked knowns-dev CVEs.
- CVE-2026-86439high 8.8EPSS 0.8%
- CVE-2026-86538high 7.5EPSS 0.7%
- CVE-2026-86541high 8.3EPSS 0.5%
- CVE-2026-86542critical 9.1EPSS 0.5%
- CVE-2026-86543critical 9.8EPSS 0.4%
- CVE-2026-86544high 8.1EPSS 0.3%
- CVE-2026-86539high 7.2EPSS 0.2%
- CVE-2026-86540high 7.8EPSS 0.1%
Products affected
Threadlinqs normalises CPE and CNA product records across all 8 CVEs; 1 distinct knowns-dev product is affected. The most frequently affected:
- knowns 8 CVEs
Threat activity
No tracked threat campaign references knowns-dev products or CVEs yet. Vulnerability records are still monitored for exploitation and linked as campaigns are ingested.
How to prioritise knowns-dev patching
This order follows the data Threadlinqs holds for knowns-dev, not a generic severity checklist:
- No knowns-dev CVE is in CISA KEV yet, so rank by exploit probability instead.
- Outside KEV, the highest EPSS scores are CVE-2026-86439 (0.8%), CVE-2026-86538 (0.7%), CVE-2026-86541 (0.5%).
- 2 CVEs score Critical and 6 High on CVSS v3 (maximum 9.8, average 8.3); 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-10-05 and refresh daily.