CVE tracker

Every CVE published since 1999, counted by day from the official CVE List. Rebuilt daily; counts run through Nov 17, 2026.

Published in 2026 so far
99,445

139% more than 2025 by the same date

2026 on pace for
≈ 113,248

At the pace of the last five years

Published in 2025
48,150

408,322 since 1999

Last 30 days
17,018

About 567 a day

CVEs published per month

By
Range
Show
05,00010K15K20K20002002200420062008201020122014201620182020202220242026on pace for ≈ 17,154

The dashed red segment is November 2026, still in progress, drawn to where it lands at the pace of recent months.

Last 90 days

The busiest day on record is Oct 13, 2026, with 2,291 CVEs.

01,0002,0003,000AugSepOctNov

By year

Severity

The highest CVSS rating in each record, from the publisher or CISA. 51% of 2026’s CVEs are critical or high.

2026
2025
  • Critical 10,825
  • High 40,343
  • Medium 39,111
  • Low 4,013
  • No CVSS score 5,153

218 of 2026’s CVEs are in CISA’s Known Exploited Vulnerabilities catalog.

Most common weaknesses

Share of the 91,192 CVEs from 2026 that name a CWE. A CVE can name more than one.

  1. 1Cross-site scripting CWE-798,551 9%#1 in 2025
  2. 2Missing authorization CWE-8625,526 6%#4 in 2025
  3. 3Improper access control CWE-2844,650 5%#7 in 2025
  4. 4SQL injection CWE-894,260 5%#2 in 2025
  5. 5Use after free CWE-4163,434 4%#13 in 2025
  6. 6Path traversal CWE-223,227 4%#9 in 2025
  7. 7Incorrect authorization CWE-8632,632 3%not in 2025’s top 15
  8. 8Out-of-bounds read CWE-1252,629 3%not in 2025’s top 15
  9. 9Information exposure CWE-2002,557 3%#14 in 2025
  10. 10Authorization bypass through user-controlled key CWE-6392,411 3%not in 2025’s top 15
  11. 11Server-side request forgery CWE-9182,332 3%not in 2025’s top 15
  12. 12Heap-based buffer overflow CWE-1222,273 2%not in 2025’s top 15
  13. 13OS command injection CWE-782,271 2%#10 in 2025
  14. 14Improper input validation CWE-202,138 2%not in 2025’s top 15
  15. 15Code injection CWE-942,098 2%#6 in 2025

Who publishes them

The CVE Numbering Authorities that published the most of 2026’s CVEs.

  1. 1GitHub13,167 13%
  2. 2VulnCheck10,859 11%
  3. 3Linux kernel8,284 8%
  4. 4VulDB6,414 6%
  5. 5Patchstack5,564 6%
  6. 6Microsoft5,535 6%
  7. 7Oracle4,732 5%
  8. 8Google Chrome4,175 4%
  9. 9Wordfence3,986 4%
  10. 10MITRE3,777 4%

15,369

CVEs published in 2026 so far are access control bugs: missing or broken authorization checks and IDOR. That is 3.3× the 4,706 in all of 2025.

Find them in your code before they get a CVE.

Elliot reads your repository like an attacker. It follows each request from the entry point to the line that breaks, checks who can reach it, and puts the finding on your board with the request that triggers it and the fix.

Run a free scan

CVEs per year

YearCVEsChangeCriticalHighKnown exploited
2026 (so far)99,44510,82540,343218
202548,150+21%4,11215,762197
202439,924+38%3,79113,904161
202328,847+15%2,3558,136166
202224,999+24%1,6695,684131
202120,177+10%7623,577215
202018,363+6%5082,396146
201917,308+5%2241,041129
201816,510+13%17563876
201714,642+127%13622689
20166,457−1%126854
20156,494−18%135547
20147,928+53%58534
20135,187−2%105435
20125,288+27%103922
20114,150−11%4259
20104,639−19%73623
20095,732+1%93114
20085,673−21%7166
20077,211+5%18112
20066,885+3%12132
20056,708+316%472
20041,612+32%071
20031,223−28%111
20021,690+28%130
20011,323−8%010
20001,437+349%100
19993203120

How the numbers are counted

Questions

How many CVEs have been published in 2026?

99,445 through Nov 17, 2026, on pace for about 113,248 by the end of the year. That is already more than the 48,150 published in all of 2025.

How many CVEs were published in 2025?

48,150, up 21% from 2024. 4,112 were rated critical and 15,762 high, and 197 are in CISA’s Known Exploited Vulnerabilities catalog.

How many CVEs were published in 2024?

39,924, up 38% from 2023. 3,791 were rated critical and 13,904 high, and 161 are in CISA’s Known Exploited Vulnerabilities catalog.

What is a CVE?

A CVE (Common Vulnerabilities and Exposures) record is a public identifier, like CVE-2024-3400, for one vulnerability in a specific product. CVE Numbering Authorities (vendors, security companies, open source projects and coordinators) reserve the ID, then publish the record with a description, affected versions and usually a severity score.

Why are so many more CVEs being published?

More organizations publish CVEs than ever, and the largest publish thousands a year. In 2026 the three biggest so far are GitHub, VulnCheck, Linux kernel, with 32,310 CVEs between them, 32% of the year’s total.

What does this tracker count?

Every record in the official CVE List whose state is PUBLISHED, on the UTC day of its publication date. Rejected records (19,177 so far) are left out. A record counts once, in the period it was first published, even if it is updated later.

How often is it updated?

Every day. The CVE Program publishes a snapshot of the full list at midnight UTC, and the tracker is rebuilt from it each morning, so counts run through the previous day.

Can I use the data?

Yes. Download the daily or monthly counts as CSV, or the full dataset as JSON, from the links under the chart, or embed the chart on your own site. Please link back to this page.