Exploitation timeline
Threadlinqs has recorded 10 libexpat project CVEs published between and . The busiest month was 2026-06 (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 libexpat project CVEs.
- CVE-2026-56403medium 6.9
- CVE-2026-56404medium 6.9
- CVE-2026-56405medium 6.9
- CVE-2026-56406medium 6.9
- CVE-2026-56407medium 6.9
- CVE-2026-56408medium 6.9
- CVE-2026-56410medium 6.9
- CVE-2026-56411medium 6.9
- CVE-2026-56409medium 6.5
- CVE-2026-56412medium 4.9
Products affected
Threadlinqs normalises CPE and CNA product records across all 10 CVEs; 1 distinct libexpat project product is affected. The most frequently affected:
- libexpat 10 CVEs
Threat activity
No tracked threat campaign references libexpat project products or CVEs yet. Vulnerability records are still monitored for exploitation and linked as campaigns are ingested.
How to prioritise libexpat project patching
This order follows the data Threadlinqs holds for libexpat project, not a generic severity checklist:
- No libexpat project CVE is in CISA KEV yet, so rank by exploit probability instead.
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.