CVE Trends To Watch: AI, Bug Hunters, And The Time To Patch
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: CVE Trends To Watch: AI, Bug Hunters, And The Time To Patch on ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on office and shipping supplies

  • Business-only prices and quantity discounts
  • Tax-exempt purchasing
  • Multiple users, one account, clear invoices
As an affiliate, we earn on qualifying purchases.

TL;DR

ThorstenMeyerAI.com’s analysis of public vulnerability records counts 13,934 CVEs published from Oct. 1 to Oct. 25, 2026, more than three times the total for all of October 2025. The data shows a sharp rise in disclosures, but does not establish how much AI contributed or how many vulnerabilities are being exploited; the analysis points to patching as a key concern.

13,934 new CVE records were published from Oct. 1 through Oct. 25, 2026, according to an analysis by ThorstenMeyerAI.com, a count more than three times the 4,389 records in all of October 2025. The analysis says the increase reflects a larger volume of reported vulnerabilities, but public records do not show how much artificial intelligence contributed or how many of the newly disclosed flaws are being exploited.

The analysis queried the U.S. National Vulnerability Database API for CVE records by publication date and cross-checked October entries against CVE.org. The sources showed 13,766 October records and 202 later rejected records, for a total of 13,934 records in the analysis’s October 1–25 count. The figures were retrieved Oct. 26. The author also reports that 88,772 CVEs had been published so far in 2026, 78% more than in all of 2025.

The increase was not evenly distributed across the organizations named in the records. Microsoft’s October count rose from 180 records in October 2025 to 1,455 in October 2026; Oracle rose from 78 to 1,078, and GitHub from 276 to 1,159. VulnCheck rose from 163 to 2,085, while Linux kernel records increased from 660 to 925. The analysis attributes much of the overall increase to several large vendors and vulnerability-data organizations, rather than a uniform rise across all software.

The author found that 6,346 of the 13,934 records named a finder. Two hundred records, or 1.4%, explicitly credited an AI lab or AI security firm as a finder, reporter or tool. The analysis cautions that this is a minimum visible in the record data, not a measure of AI’s full contribution. Separately, Anthropic’s disclosure dashboard, as cited in the report, listed 6,157 vulnerabilities reported to maintainers and 516 patched to the company’s knowledge.

At a glance
reportWhen: Published Oct. 26, 2026; figures retrie…
The developmentAn analysis published Oct. 26 reports a steep increase in CVE disclosures during 2026 and highlights limited patching among vulnerabilities reported by Anthropic.
Thorsten Meyer AI
NVD + CVE.org · data to 25 Oct 2026

Infographic 01 · How big the CVE wave really is

The CVE chart is real. Steep, not parabolic.

New vulnerability records have tripled year over year. A handful of big vendors and clearinghouses drive the jump, and the growth rate cooled in October.

13,934new CVE records, 1–25 Oct 2026
3.2×all of October 2025 (4,389)
88,772in 2026 so far vs. 49,972 in all of 2025
+11%daily rate, Oct vs. Sep: growth is cooling

New CVE records per month

January 2024 – 25 October 2026 · phones show the last 13 months

0
5k
10k
15k
3.6k
4.4k
15.1k
13.9k*
Jan ’24Jul ’24Jan ’25Jul ’25O’25N D J’26F M A M J J A S O’26
2024–20252026September 2026 (record)* October 2026: 1–25 Oct only
+18%Jun vs. May
+20%Jul vs. Jun
+28%Aug vs. Jul
+22%Sep vs. Aug
+11%Oct vs. Sep

Growth of new CVEs per day versus the previous month. Steep, but the acceleration slowed in October: not “parabolic”.

Who publishes the jump

records by CVE Numbering Authority, October vs. October

  • MicrosoftOct 2025 → Oct 2026180 → 1,455
  • OracleOct 2025 → Oct 202678 → 1,078
  • VulnCheckOct 2025 → Oct 2026163 → 2,085
  • GitHub (open-source maintainers)Oct 2025 → Oct 2026276 → 1,159
  • Linux kernelOct 2025 → Oct 2026660 → 925

Microsoft’s October Patch Tuesday fixed a record 1,413 CVEs (SecurityWeek (14 Oct 2026)). The Linux kernel grew far less.

Not a backlog dump

checks on the October 2026 records

  • 98% carry a 2026 ID
  • 15 days median from reserving an ID to publishing it
  • 217 numbering authorities published, vs. 163 in Oct 2025
  • 202 records were later rejected (counted, as NVD does)
  • ~17,000 if October’s pace holds: a projection, not a count

Sources: NVD CVE API 2.0 (counts by publication date, all statuses, queried 26 Oct 2026); CVE.org records (credits field, fetched 26 Oct 2026); SecurityWeek (14 Oct 2026). Own analysis; raw files and queries in the kit.
Powered by Thorsten Meyer AI

Disclosure Is Outpacing Known Fixes

A higher CVE count means more vulnerabilities are being publicly recorded; it does not, on its own, show that attacks have increased at the same rate. The distinction matters to organizations deciding how to prioritize security work: a disclosed flaw can remain a risk if affected software is not updated, but a publication count alone does not reveal exposure, severity or whether a system is vulnerable.

The patching figures cited in the analysis point to a potential gap between discovery and remediation. Of the 6,157 vulnerabilities Anthropic says it reported to maintainers, it knew of 516 patches at the time described. That figure does not establish that the remaining reports are unpatched everywhere: the status may have changed, fixes may not have been reported back, and the dataset covers one company’s disclosures rather than all vulnerabilities.

For security teams, the practical takeaway is to pair disclosure monitoring with verification of affected products, vendor advisories and available updates. For policymakers and researchers, the figures underline the need for better reporting on discovery methods, remediation status and exploitation, rather than relying on CVE totals as a proxy for risk.

De'Longhi Magnifica Duo Fully Automatic Espresso Machine with Milk Frother, Silver

De'Longhi Magnifica Duo Fully Automatic Espresso Machine with Milk Frother, Silver

As an affiliate, we earn on qualifying purchases.

How the 2026 Counts Were Built

The report counts records by their publication date, using NVD API data from January 2022 onward and a cross-check against CVE.org for October. It says 98% of the October records had a 2026 CVE identifier and gives a median of 15 days between reserving an identifier and publication. Those details support the author’s view that the increase is not simply a release of old records, though they do not explain the cause of the surge.

The growth rate also varied by month. The analysis reports daily publication rates rising 20% from June to July, 28% from July to August and 22% from August to September; the rate increase through Oct. 25 was about 11%. Its estimate that October could end near 17,000 records is a projection, not an observed total. A podcast episode published Oct. 25 described the chart as “going parabolic”; the report argues that the data showed a continued climb but slower acceleration in October.

Public vulnerability records identify who published or coordinated a disclosure more consistently than who first found a flaw. CVEs are generally published through a CVE Numbering Authority, often after a vendor or maintainer has been notified. That process makes the records useful for tracking disclosures, but incomplete for measuring the role of AI tools or the identity and location of researchers.

“If October’s pace holds, the month ends near 17,000.”

— Thorsten Meyer, describing the October estimate

AI’s Share and Exploitation Remain Unclear

The CVE data cannot establish how much AI was involved in finding vulnerabilities. More than half of October’s records—54%—did not name a finder, while 1.4% explicitly credited an AI lab or security firm. The report says the latter is a floor because records may omit AI assistance or describe it in ways that are not captured by the analysis. Anthropic and OpenAI also report security research activity, but their figures use different methods and cannot be directly compared with the full CVE count.

The supplied source material does not include the full CISA Known Exploited Vulnerabilities comparison it begins to describe, so it does not support a complete assessment of exploitation trends. Nor does it provide a comprehensive patch-status total across vendors. The October count is partial, the end-of-month figure is projected, and rejected entries are included in the author’s total after being separated from the 13,766 records counted as published in October.

Track October’s Final Count and Patches

The next clear data point will be the completed October publication count, which can be compared with the author’s estimate of nearly 17,000. Updates to vendor advisories and maintainer reports may also clarify how many of the vulnerabilities cited by Anthropic have been fixed since its dashboard was described in the analysis.

Readers should watch for further reporting that separates CVE publication volume from confirmed exploitation, identifies the affected products and tracks remediation. Until those measures are available across a broader set of sources, the record surge is evidence of increased disclosure activity—not a standalone measure of attackers’ success or AI’s share of vulnerability discovery.

Key Questions

How many CVE records were counted in October 2026?

The analysis counted 13,934 records from Oct. 1 through Oct. 25, including 13,766 October records and 202 records it says were later rejected. It is not a final full-month count.

Does the CVE surge prove that AI is finding most vulnerabilities?

No. The analysis found explicit AI-related credit on 200 records, or 1.4%, but 54% of records named no finder. The author says the records cannot establish AI’s full contribution.

What does the report say about patching?

It cites Anthropic’s dashboard as listing 6,157 vulnerabilities reported to maintainers and 516 patched to the company’s knowledge. The figure is not a complete patch-status count across software and may not reflect later updates.

Does a higher CVE count mean attacks are rising at the same rate?

No. CVE publication counts measure disclosed records, not confirmed exploitation. The supplied analysis does not provide enough complete exploitation data to determine whether attacks rose in line with disclosures.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

How SenseTime’s AI Capabilities Are Reinforcing Its Market Position And Profitability

SenseTime reports its first profit under IFRS, driven by leadership in generative AI and computer vision, marking a key milestone in its transformation.

AI Is Pushing More Paperwork Into Britain’s Bureaucratic System

Sky News reports rising written complaints and claims since ChatGPT launched, as officials warn AI is increasing pressure on Britain’s paperwork-heavy services.

From Lawsuit To AI Freeze: What Nonprofits Want The Court To Order

Four nonprofit groups sued five AI developers in California, seeking a halt to systems more capable than those they had on Nov. 12.

A Construction App’s AI Business Replay, Clearly Labeled as Simulation

The AI Company Emulator replays an emulated AI team running the construction-site app GewerkTon day by day, every decision visible and clearly labelled as a simulation.