News · eGov

The number of vulnerabilities added to the CISA Known Exploited Vulnerabilities catalog between January and mid-November 2026 reached 298, compared with 221 over the same period in 2025.
✦ AI SUMMARY 30-second read

- CISA KEV additions totalled 298 between 1 January and 17 November 2026, up from 221 in the same window of 2025, a rise of 77 entries or approximately 35%.
- Of the catalog's 1,782 total entries, 361 carry a ransomware-linked flag, representing a 20% lifetime share that covers all years the list has existed, not only 2026 additions.
- Recent batches span storage appliances, AI gateway software, research data platforms and enterprise network tools, illustrating how the catalog now reaches well beyond firewalls and VPN gateways.
Why it matters: A faster pace of confirmed exploited-vulnerability listings signals that unpatched public-facing software is an increasingly common entry point for attackers.

This summary was generated by AI. Editors may review and update it.
The CISA Known Exploited Vulnerabilities catalog recorded 298 additions between 1 January and 17 November 2026, against 221 over the equivalent period of 2025. The difference of 77 entries represents a rise of roughly 35%.

Four further flaws were listed on 18 November 2026 and four more on 20 November, meaning the 298 figure is already a historical snapshot. The 20 November batch covered SAP NetWeaver, Cisco Expressway, VMware vCenter and Apache Roller.
What the count measures
The catalog is a curated list rather than a comprehensive feed of every attack observed. CISA requires three conditions for an entry: a CVE identifier, confirmed evidence of active exploitation, and clear mitigation guidance. Flaws missing any one of those criteria do not appear, regardless of how widely they are discussed.
A higher addition count can reflect more exploitation activity, faster verification by the agency, improved fix documentation from vendors, or stronger threat intelligence submissions. The raw figure alone cannot separate those causes.
The 35% increase applies only to new additions during the comparison window. The separate ransomware flag, which marks 361 of the catalog's 1,782 total entries as known ransomware-linked, represents a lifetime share accumulated across every year the list has existed. The two percentages describe different things and should not be combined.
What recent additions show
The 18 November batch covered a storage operating system, an AI gateway, a Java web-services library and a research data platform. Three of the four entries carried no confirmed ransomware association; exploitation themes included credential theft, access to cloud data, cryptomining and LLMjacking, the abuse of hijacked access to AI services.
One entry stands out for its age. CVE-2024-10441, affecting Synology DiskStation Manager, was added despite the flaw being nearly a year old at the time of listing. Reporting linked it to active ransomware deployment against network-attached storage devices. The case illustrates that KEV additions are not restricted to recently disclosed vulnerabilities.
Earlier November batches touched Cisco BroadWorks, Barracuda, Microsoft Outlook, a Chromium component, UnrealIRCd and Check Point products. Within a single month the catalog reached email security, telephony, configuration management, browsers and NAS software.
What it means for defenders
A separate dataset points in a similar direction. A Beazley Security release dated 19 November 2026 stated that ransomware incidents rose 38% in the third quarter of 2026, and that the share of cases beginning with exploitation of a vulnerability doubled from 14% in the second quarter to 28% in the third. Those figures describe one firm's caseload and are not industry-wide totals.
Binding Operational Directive 26-04 requires civilian federal agencies in the United States to remediate KEV vulnerabilities on publicly exposed assets within defined timeframes. The directive does not bind private organisations, though many apply the same deadlines voluntarily to internet-facing systems.
For security teams, the practical implication is prioritisation. The catalog answers a question that severity scores alone cannot: whether a flaw is being actively exploited now. Teams unable to inventory every internet-facing asset, including storage appliances and AI serving infrastructure, cannot assess whether a given listing applies to them.
What happens next
The catalog is updated several times each week, so any annual total will continue to shift. The catalog is publicly available in CSV and JSON formats, allowing teams to run their own counts against any date window.
Elets will update this story as further additions are confirmed.