Resources · Vulnerability management, CVE, Continuous monitoring, External perimeter

2026 CVE Count Through October Passes 2024 and 2025 Combined

By the end of October, the cve.tools index had counted more CVE records for 2026 than for the two previous years together. What the numbers show, what AI has to do with it, and why a yearly check of your internet-facing systems no longer keeps up.

Our view

A longer CVE list gives your team more records to check against the software it runs. This year there are more than twice as many as in the same months of 2025, and internet-facing systems keep changing between checks. We would not rely on one external check a year to keep up with both.

IntruForce

A CVE ID is a shared identifier for a publicly disclosed vulnerability. The cve.tools index counted 95,094 CVE records published from January through October 2026. That is more than 2024 and 2025 combined (93,078), before November and December are counted.

How many CVEs were published through October

The monthly count rose overall, from 5,244 in January to 8,314 in June and 17,650 in October, with small dips in February and April. October alone was 3.9 times October 2025. Almost six in ten of this year's CVEs were published from July to October.

The index shows +125% for 2026. That figure compares January–October with the same ten months of 2025 (42,337). Against the whole of 2025 (51,302), the first ten months of 2026 are already about 85% higher, although that sets ten months against a full year. Other counters use different methods and give different totals; we use one index throughout so that the comparisons match. cve.tools is a third-party index that combines several CVE sources and counts records by publication date.

In June, the Forum of Incident Response and Security Teams (FIRST), an international organization, revised its forecast for all of 2026 up to about 66,000 CVEs. By the cve.tools count, the year passed that figure in September. The monthly figures are on cve.tools/trends.

Why the count rose

The increase reflects both more discoveries and changes in how vulnerabilities are recorded. FIRST points to the recording side: GitHub Security Advisory volume up 449% year on year, a 3,119% rise in IDs from VulnCheck, which may assign them when no other authority does, partly clearing a backlog, and more products being tracked. It also names AI-assisted discovery.

Mozilla's Firefox work shows one way AI contributes. Mozilla fixed 423 security bugs in its April releases, against 20 to 30 a month through 2025; 271 of them, fixed in Firefox 150, were identified with Anthropic's Claude Mythos Preview. These are bug counts: Mozilla groups some bugs under one CVE record. In May, Microsoft's security response team wrote that AI is changing the scale and speed of vulnerability discovery and that it expects its monthly releases to keep trending larger for some time. cve.tools attributed 1,487 October CVE records to Microsoft, more than to any other vendor that month; that is a count for the whole month, not the number of fixes in October's Patch Tuesday.

These reports do not show what share of 2026 records involved AI, and we will not guess one. They do show cases where AI helped vendors and researchers find more flaws, faster, in software already in wide use. FIRST's forecast points to continued growth, but the final 2026 total is not known yet.

CVE records rose faster than CISA's KEV additions

CISA, the US cybersecurity agency, keeps the KEV catalog of vulnerabilities it knows have been exploited in real attacks; it is not a complete list of every exploited vulnerability. From January to October 2026, CISA added 282 entries, against 245 in all of 2025 (15% more). Over the same comparison, CVE records went from 51,302 in all of 2025 to 95,094 in January–October 2026 (about 85% more). Over the last 12 full months, the index counted one KEV addition for every 332 CVEs published; the two groups differ, since KEV can add vulnerabilities published years earlier. FIRST's June update, which covers the first half of the year and uses a different measure, points the same way: when it filtered the volume to vulnerabilities in KEV or with an EPSS score (an estimate of the chance of exploitation in the next 30 days) above 10%, that set had not materially increased.

More than twice as many new CVE records were published in January–October 2026 as in the same months of 2025; which of them matter depends on the software you run and the systems you expose. For the 20 October CVEs already in KEV, the median time from publication to listing was five days. We showed the same pattern in More vulnerabilities, less time.

Why a yearly external check falls behind

A yearly external check gives you a snapshot of which systems could be reached from the internet on that day and which issues were found at that time. That snapshot gets older as sites, subdomains and services appear and move, as we described in annual pentest or continuous perimeter monitoring. Meanwhile this year brought about 9,500 new CVEs a month on average, over 17,000 in October, for software you may already run.

Monitoring your internet-facing systems repeats the check on your plan's schedule. Each check can show your team:

  • which websites, subdomains and services respond from the internet, including new ones;
  • which software and versions they show to anyone who looks;
  • which known vulnerabilities match those versions, and which of them CISA lists as attacked;
  • what changed since the last check.

Monitoring covers what can be reached from the internet, not your internal network. A version match is a lead your team still has to confirm. Monitoring does not fix issues; it helps your team decide what to look at first.

Three questions to ask about your internet-facing systems

  1. Do we have one current list of everything we expose to the internet, including what external providers and subsidiaries run?
  2. When a critical vulnerability is published, how do we learn whether it affects one of those systems, and how long does that take?
  3. When was each of those systems last checked from the outside?

Sources

  • CVE and KEV figures: cve.tools trends and the October 2026 monthly report, computed 2 November 2026, 05:00 UTC; trends page read again on 5 and 13 November 2026. CVEs counted once per ID across all merged sources, by publication date; KEV by date added to CISA's catalog. 2026: 95,094 (Jan–Oct; on 13 November the page also showed 3,705 November CVEs so far, 98,799 in all); Jan–Oct 2025: 42,337; full 2025: 51,302; 2024: 41,776. KEV additions: 282 (Jan–Oct 2026), 245 (2025); last 12 full months: 104,059 CVEs, 313 KEV additions. October: 20 October CVEs in KEV, median 5 days to listing.
  • FIRST Forecasting team (Jerry Gamblin, Eireann Leverett): 2026 vulnerability forecast update, 15 June 2026: about 66,000 CVEs for 2026; growth drivers; burden filtered to KEV or EPSS above 10% flat.
  • Mozilla Hacks: «Behind the Scenes: Hardening Firefox with Claude Mythos Preview», 7 May 2026.
  • Microsoft Security Response Center: «A note on this month's Patch Tuesday», 12 May 2026.

Get started

Know your risks before attackers find them.

Discover your external assets, identify security weaknesses and check for exposed corporate credentials with a free SeguriScan pilot. Get access to the platform, findings and reports to understand what needs attention.

  • Nothing to install
  • No access to your internal network
  • No active testing without your approval

We’ll contact you by email to discuss the pilot and agree on the next steps. No obligation to proceed. What’s included in the pilot →

By submitting this form, you acknowledge that IntruForce will process your personal data to respond to your request. See our Privacy Policy for details.