CVE Census

Daily · data as of 16 Nov 2026

The state of global vulnerability research, from every public source, joined.

407 052 published CVEs. 35 655 with a public exploit. 1 802 known to be exploited in the wild. One record per CVE, followed from the day it was reserved to the day it was patched or attacked.

Key findings

What the joined data shows

  1. 01
    Volume CVEs published per year

    98 175 CVEs so far in 2026, +137% on the same period of 2025. At this pace the year ends near 111 981.

  2. 02
    Exploitation Days from publication to first 'exploited' listing

    Half of the 914 exploited CVEs published since November 2021 were listed within 7 days. 30% were already being exploited when published (zero-days), 51% within a week.

  3. 03
    Exploitation Did a public exploit come first?

    Of 916 exploited CVEs (published since November 2021), 39% never had a public exploit: attackers did not need one.

  4. 04
    Prediction Effort against coverage: EPSS or CVSS

    From the scores of November 2025: patching every CVE with EPSS ≥ 10% meant 6.9% of CVEs and caught 49% of those exploited in the next year. Patching every CVSS ≥ 9 meant 13% of CVEs and caught 31%. A small sample: 75 CVEs scored that day were first listed in the following year.

  5. 05
    Records What NVD did with each month's CVEs

    18 172 CVEs are waiting for NVD analysis and 63 265 are deferred. Of the last 12 months' CVEs, NVD has analysed 44%.

  6. 06
    Records CNA score minus NVD score

    Where both scored (since 2020, 80 816 CVEs), they agree exactly 25% of the time. NVD is at least 2 points higher in 21% of cases; the CNA in 6%.

  7. 07
    Who Most credited researchers, all time

    25 620 distinct names are credited in CVE records. 58% of them appear once; the top 1% of names account for 38% of credits.

  8. 08
    Open source Malicious packages reported per month

    241 648 malicious packages are recorded in OSV, 93% of them on npm. These are not bugs: they are packages published to steal or attack.

  9. 09
    Exploitation Most claimed proofs of concept on GitHub

    CVEs with ten or more PoC repositories are exploited in 51% of cases; with one to nine, 6%. Many repositories are fakes or scanners.

  10. 10
    Weaknesses Most common weaknesses, last 12 months

    The most common is CWE-79: Improper Neutralization of Input During Web Page Generation. 6% of the year's CVEs name no CWE.

This month

What is new

Updated every day from the sources below. Every CVE links to its full record.

# Newly listed as exploited

34 CVEs were first listed as exploited in the last 30 days.

CVE-2026-11471313 Nov 202658.60.51%The labeled-response module in UnrealIRCd 6.0.0 before 6.2.7.1 does not escape the IRCv3 "label" message tag w
CVE-2026-12303913 Nov 202617.82.2%Local privilege escalation to root in the DynamicCLI daemon via local world-writable control socket
CVE-2026-11156010 Nov 202688.69.1%OS Command Injection in Barracuda Appliances
CVE-2026-11179310 Nov 2026254.30.64%Openwave Webtop Media Transcoder does not enforce administrator-defined file type restrictions to restrict the
CVE-2026-11660610 Nov 202689.311%Authentication Bypass Allows Global Configuration Restore in Barracuda Email Security Gateway
CVE-2026-12419410 Nov 202606.51.6%Microsoft Outlook Spoofing Vulnerability
CVE-2026-12535010 Nov 202608.80.96%Use after free in XML in Google Chrome prior to 157.0.8103.50 allowed a remote attacker to execute arbitrary c
CVE-2026-2032010 Nov 2026837.50.98%A vulnerability in the Open Client Interface (OCI) XML Parser of Cisco BroadWorks could allow an unauthenticat
CVE-2026-1028959 Nov 202659.80.52%GPUStack: Authentication bypass via trusted loopback source (reverse-proxy TCP peer or X-GPUStack-Real-IP header) grants unauthenticated admin
CVE-2026-1167799 Nov 202649.82.5%FreeSWITCH: Inbound SIP MESSAGE can select the api chat proto and run FreeSWITCH API commands
CVE-2026-1231589 Nov 202648.119%sshd in OpenSSH before 10.6p2 on Linux, when musl libc is used without PAM, lacks a workaround for a password
CVE-2026-1232189 Nov 202629.80.53%IBM Aspera Faspex Authorization Bypass

# Biggest EPSS rises in 30 days

CVEs whose predicted chance of exploitation rose most in a month.

CVE-2026-756504.0%99%YesAdobe Commerce | Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336)
CVE-2026-314313.4%98%Yescrypto: algif_aead - Revert to operating out-of-place
CVE-2026-344866.6%99%YesApache Tomcat: Fix for CVE-2026-29146 allowed bypass of EncryptInterceptor
CVE-2026-435002.3%94%norxrpc: Also unshare DATA/RESPONSE packets when paged frags are present
CVE-2026-30554.0%91%YesInsufficient input validation leading to memory overread
CVE-2026-283181.9%87%YesSolarWinds Serv-U Unauthenticated Denial of Service Vulnerability
CVE-2026-356169.1%94%YesA improper access control vulnerability in Fortinet FortiClientEMS 7.4.5 through 7.4.6 may allow an unauthenti
CVE-2026-422085.8%89%YesLiteLLM: SQL injection in Proxy API key verification
CVE-2026-1051330.85%84%YesAhsay AhsayCBS API ApiStructsAction.java checkSysPwd improper authentication
CVE-2026-3419715%98%YesApache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Authenticated users could perform RCE via Jolokia MBeans

# Newest critical CVEs

1 439 CVEs scored critical in the last 30 days.

CVE-2026-9366416 Nov 202610.03DSDeserialization of Untrusted Data vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x
CVE-2026-5399816 Nov 202610.0GitHub_MPhoenix: Format String Injection in applyChatTemplate
CVE-2026-12935415 Nov 202610.0VulDBD-Link DIR-600L HNAP cgibin hnap_main stack-based overflow
CVE-2026-12944415 Nov 202610.0VulDBD-Link DSL-6740C FTP Daemon ftpd_conf.php hard-coded credentials
CVE-2026-12935314 Nov 202610.0VulDBD-Link DIR-600L authentication.cgi authenticationcgi_main stack-based overflow
CVE-2026-12935114 Nov 202610.0VulDBTRENDnet TEW-657BRM mini_httpd setup.cgi sprintf out-of-bounds write
CVE-2026-7703316 Nov 20269.93DSOS Command Injection vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x
CVE-2026-1973216 Nov 20269.93DSOS Command Injection vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release 3DEXPERIENCE R2023x through Release 3DEXPERIENCE R2026x
CVE-2026-12704815 Nov 20269.8WPScanLazy Blocks < 3.0.0 - Unauthenticated RCE
CVE-2026-12579515 Nov 20269.8PatchstackWordPress Estatik plugin <= 4.3.6 - Local File Inclusion vulnerability

Volume

How many vulnerabilities get a CVE, and how fast that is growing

Every published CVE record since 1999, by publication date. Rejected IDs are counted separately; reserved IDs that were never published are not visible.

Published CVEs, all time
407 052
So far in 2026
98 175
Same period last year
41 459+137%
2026 at this pace
111 981

Volume on its own page →

Growth

# CVEs published per year

98 175 CVEs so far in 2026, +137% on the same period of 2025. At this pace the year ends near 111 981.

  • Published
  • Projected rest of year
050k100k1999200220052008201120142017202020232026
Source: CVE List V5. The current year's projection assumes the year-to-date daily rate holds.

# Every month since 2016

407 052 published CVEs in all; the busiest single day was 13 October 2026 with 2 291.

05k10k15k20k2016Aug ’17Mar ’19Oct ’20May ’22Dec ’23Jul ’25CVEs published

Rhythm

# The last 90 days

Daily publication counts. Weekends are quiet; big batch days are usually one CNA publishing a backlog.

01k2k18 Aug27 Aug5 Sep14 Sep23 Sep2 Oct11 Oct20 Oct29 Oct7 Nov16 Nov

# Which weekday CVEs are published

Share of the last 12 months' CVEs by publication weekday (UTC).

0%10%20%30%MondayTuesdayWednesdayThursdayFridaySaturdaySunday

Severity

# Severity mix by year

Share of each year's CVEs by severity: the CNA's score where given, else CISA's, else NVD's.

  • Critical
  • High
  • Medium
  • Low
  • No score
0%25%50%75%100%201020122014201620182020202220242026

Process

From an ID being reserved to the record being published; withdrawn IDs; how many organisations take part, and how concentrated publishing is.

# Days from reserving an ID to publishing it

Reserving comes when a CNA starts handling a report; publishing after the fix. The gap is the embargo, roughly.

  • Median
  • 90th percentile
0 d100 d200 d300 d400 d201520172019202120232025Median90th percentile

# Published and rejected IDs, by ID year

Rejected IDs were reserved and later withdrawn: duplicates, not vulnerabilities, or never used.

  • Published
  • Rejected
025k50k75k100k201020122014201620182020202220242026

# How many CNAs publish

Distinct CNAs that published at least one CVE that year.

0200400201020122014201620182020202220242026

# How concentrated publishing is

Share of each year's CVEs published by the largest CNA, and by the ten largest.

  • Ten largest CNAs
  • Largest CNA
0%25%50%75%100%2014201620182020202220242026Ten largest CNAsLargest CNA

Exploitation

From publication to public exploit to attack

When CVEs get a public exploit, when they are seen exploited in the wild, and which come first. 'Exploited' means listed by CISA KEV, ENISA's EUVD, VulnCheck KEV or Google Project Zero; nothing else.

Exploited CVEs since Nov 2021
914
Median days to first listing
7
Exploited by publication day
30%
Exploited without any public exploit
39%

Exploitation on its own page →

The funnel

# From published to exploited

Of 243 415 CVEs published since November 2021, 3.8% have a public exploit or proof of concept and 0.40% are known to be exploited in the wild.

  1. Published 243 415
  2. Public exploit or PoC (Exploit-DB, Metasploit, GitHub) 9 175
  3. Scanner template (Nuclei) 3 027
  4. Metasploit module 881
  5. Exploited in the wild (any list) 916

Bar lengths on a logarithmic scale.

Timing

CVEs published since 3 November 2021, when CISA’s list started; older CVEs were added to it in bulk, which would distort the timing.

# Days from publication to first 'exploited' listing

Half of the 914 exploited CVEs published since November 2021 were listed within 7 days. 30% were already being exploited when published (zero-days), 51% within a week.

  • Before publication
  • Same day
  • After
0501001502000.1%> 1 yr before2.6%1–12 mo before2.1%1–4 wk before4.2%2–7 d before2.2%1 d before19%same day6.3%1 d15%2–7 d14%1–4 wk12%1–3 mo8.5%3–6 mo6.8%6–12 mo3.6%1–2 yr3.7%> 2 yr

# Days from publication to first public exploit

For 8 729 CVEs published since November 2021 with a public exploit, the median wait was 5 days; 27% had one before the CVE was published.

  • Before publication
  • Same day
  • After
05001k0.8%> 1 yr before7.5%1–12 mo before6.6%1–4 wk before8.5%2–7 d before3.4%1 d before8.5%same day6.6%1 d12%2–7 d12%1–4 wk12%1–3 mo7.6%3–6 mo6.3%6–12 mo4.5%1–2 yr3.5%> 2 yr

# Did a public exploit come first?

Of 916 exploited CVEs (published since November 2021), 39% never had a public exploit: attackers did not need one.

  1. Public exploit first, then exploited 314
  2. Exploited first, public exploit later 245
  3. Exploited, never a public exploit 356

# Median days to first exploited listing, by publication year

Recent years look faster partly because slow cases have not happened yet.

0 d50 d100 d150 d200 d202120222023202420252026

Zero-days

# Exploited CVEs per year, zero-day or not

By year of first listing; CVEs published since November 2021.

  • Exploited on or before publication
  • Exploited after publication
0100200300202120222023202420252026

# Project Zero: zero-days caught in the wild

Google Project Zero's tracker. Where it records both dates, the median time from discovery to patch was 9 days (132 cases).

0204060802014201620182020202220242026

# Whose software the in-the-wild zero-days hit

Vendors in Project Zero's in-the-wild list, all years.

  1. Microsoft 167
  2. Google 81
  3. Apple 67
  4. Adobe 29
  5. Samsung 13
  6. Qualcomm 11
  7. Mozilla 10
  8. ARM 6
  9. Sophos 3
  10. Cisco 3
  11. TrendMicro 2
  12. Oracle 2

# CISA KEV additions per year, by ransomware use

CISA marks KEV entries known to be used in ransomware campaigns.

  • Known ransomware use
  • No known ransomware use
0200400600202120222023202420252026

The lists

# Who says it is exploited

CISA lists 1 781 CVEs, ENISA 1 798. ENISA's list includes 1 781 of CISA's and adds 17 of its own; 0 are on CISA's list only.

  1. CISA KEV 1 781
  2. ENISA EUVD exploited 1 798
  3. Both CISA and ENISA 1 781
  4. ENISA only 17
  5. CISA only 0
  6. Project Zero in-the-wild 0-days 414

Proof-of-concept hype

# Most claimed proofs of concept on GitHub

CVEs with ten or more PoC repositories are exploited in 51% of cases; with one to nine, 6%. Many repositories are fakes or scanners.

CVE-2026-109618778Yes100%RCE via OOM corruption
CVE-2021-44228509Yes100%Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints
CVE-2025-55182459Yes100%–
CVE-2026-31431324Yes98%crypto: algif_aead - Revert to operating out-of-place
CVE-2026-43499194no5.4%rtmutex: Use waiter::task instead of current in remove_waiter()
CVE-2021-4034184Yes95%–
CVE-2021-41773176Yes100%Path traversal and file disclosure vulnerability in Apache HTTP Server 2.4.49
CVE-2025-29927134no99%Authorization Bypass in Next.js Middleware
CVE-2019-0708122Yes100%–
CVE-2022-0847110Yes93%–
CVE-2022-22965100Yes100%–
CVE-2024-638797no100%Openssh: regresshion - race condition in ssh allows rce/dos
CVE-2014-627196Yes100%–
CVE-2022-3019095Yes98%Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution Vulnerability
CVE-2026-11149793Yes83%Out-of-Bounds Write in Google Brotli Decoder

Prediction

Did the scores see it coming?

EPSS gives every CVE a daily probability of exploitation in the next 30 days; CVSS rates how bad a CVE would be. Both are used to decide what to patch first. Here, past scores are checked against what was later listed as exploited.

CVEs scored by EPSS today
406 741
With EPSS ≥ 10%
17 550
With EPSS ≥ 50%
4 384

Prediction on its own page →

Effort against coverage

If you had patched every CVE above a threshold, how much work would that have been, and how many of the CVEs exploited in the following year would you have caught? The dashed line is choosing at random.

# Effort against coverage: EPSS or CVSS

From the scores of November 2025: patching every CVE with EPSS ≥ 10% meant 6.9% of CVEs and caught 49% of those exploited in the next year. Patching every CVSS ≥ 9 meant 13% of CVEs and caught 31%. A small sample: 75 CVEs scored that day were first listed in the following year.

  • EPSS at or above a threshold
  • CVSS at or above a score
  • Random choice
0%25%50%75%100%0.1%0.3%1%3%10%30%100%Effort: share of all CVEs you would patch (log scale)Coverage: share of later-exploited CVEs caught≥50%≥30%≥10%≥5%≥1%≥0.5%≥0.1%CVSS ≥ 9CVSS ≥ 7CVSS ≥ 4

Calibration

# Predicted against observed, 90 days ahead

Each first-of-month snapshot since 2022, grouped by score. 'Observed' is the share first listed as exploited in the next 90 days. Of scores of 60% or more, 0.20% were followed by a first listing within 90 days, against 83% predicted. EPSS predicts exploitation activity of any kind, such as attempts seen by sensors; the lists record confirmed exploitation, mostly of new CVEs, and CVEs already listed are left out here. Read it as a ranking, not a probability of being listed.

  • Predicted (mean EPSS)
  • Observed (listed as exploited within 90 days)
0.001%0.01%0.1%1%10%100%EPSS 0–0.001Predicted 0.06%Observed 0.01%: 235 of 3 497 258EPSS 0.001–0.01Predicted 0.43%Observed 0.01%: 324 of 5 742 795EPSS 0.01–0.05Predicted 1.95%Observed 0.02%: 532 of 2 662 064EPSS 0.05–0.1Predicted 7.10%Observed 0.03%: 134 of 447 310EPSS 0.1–0.3Predicted 17.41%Observed 0.05%: 208 of 390 473EPSS 0.3–0.6Predicted 42.96%Observed 0.13%: 224 of 167 622EPSS 0.6–1Predicted 82.62%Observed 0.20%: 439 of 217 694
EPSSScoresPredictedListed within 90 daysObserved
0–0.0013 497 2580.06%2350.01%
0.001–0.015 742 7950.43%3240.01%
0.01–0.052 662 0641.95%5320.02%
0.05–0.1447 3107.10%1340.03%
0.1–0.3390 47317.41%2080.05%
0.3–0.6167 62242.96%2240.13%
0.6–1217 69482.62%4390.20%

Before the listing

# EPSS just before a CVE was listed as exploited

The last available score before listing, for 1 145 CVEs listed more than a week after publication: 43% were already at 10% or more; the median was 5.1%.

01002003009.1%0–0.1%18%0.1%–1%23%1%–5%7.6%5%–10%10%10%–30%12%30%–60%20%60%–100%

Who

Who assigns, who ships the bugs, who finds them

CVE Numbering Authorities assign the IDs; vendors are named in the records; researchers are credited by the CNA. Every name links to its own page with all its CVEs.

CNAs
566
Published in the last 12 months
426
Vendor names
25 566
Credited names
25 620

Who on its own page →

CVE Numbering Authorities

# CNAs: volume and record quality

566 organisations may assign CVE IDs; 426 published at least one in the last 12 months. The busiest was GitHub, Inc. with 13 590.

GitHub, Inc.USA13 59022 755100%100%100%49
VulnCheckUSA11 17211 830100%100%100%21
kernel.orgUSA9 34318 24536%0%100%12
VulDBSwitzerland7 03418 029100%100%100%6
PatchstackEstonia6 43019 644100%100%100%0
Microsoft CorporationUSA5 60817 05367%51%100%384
WordfenceUSA4 55312 157100%100%100%1
MITRE CorporationUSA4 539115 5823.0%1.0%100%332
OracleUSA4 15412 39756%0%100%44
ChromeUSA3 9987 4470%46%100%78
WPScanFrance2 3676 5244.0%100%100%2
IBM CorporationUSA1 9098 44169%39%100%10
Apache Software FoundationUSA1 5173 24517%76%100%35
Red Hat, Inc.USA1 44812 11226%38%95%37
Apple Inc.USA1 2707 7320%0%100%96
Adobe Systems IncorporatedUSA1 2697 89855%55%100%77
Mozilla CorporationUSA9843 1590%0%100%12
DellUSA7012 61877%74%100%3
Cisco Systems, Inc.USA6046 65353%63%100%102
Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS)USA5693 91157%84%100%8
GitLab Inc.USA4981 513100%61%100%7
Hewlett Packard Enterprise (HPE)USA4741 71549%4.0%100%2
Android (associated with Google Inc. or Open Handset Alliance)USA4575 3960%0%100%14
CPAN Security GroupCanada4394840%100%100%0
NVIDIA CorporationUSA4321 20978%71%100%0
Sources: CVE List V5, CVE Numbering Authorities. Quality columns: share of the CNA's records that include a CVSS score, a CWE and affected versions, as supplied by the CNA itself.

Countries and kinds of CNA

# Where CVEs come from: CNA country

CVEs published in the last 12 months, by the country of the CNA that assigned them (not of the vendor or researcher).

  1. USA · 211 CNAs 79 253
  2. Switzerland · 10 CNAs 7 362
  3. Estonia · 1 CNAs 6 430
  4. France · 9 CNAs 2 457
  5. Taiwan · 14 CNAs 1 030
  6. Germany · 22 CNAs 970
  7. Japan · 14 CNAs 920
  8. Canada · 7 CNAs 774
  9. China · 16 CNAs 561
  10. Spain · 10 CNAs 421
  11. India · 3 CNAs 421
  12. Türkiye · 2 CNAs 411
  13. Poland · 1 CNAs 395
  14. South Korea · 8 CNAs 372
  15. Netherlands · 6 CNAs 339

# CNAs per country

Organisations authorised to assign CVE IDs, by country.

  1. USA 294
  2. Germany 29
  3. China 24
  4. Taiwan 17
  5. Japan 15
  6. Spain 15
  7. France 14
  8. Switzerland 13
  9. Australia 13
  10. UK 12
  11. Canada 10
  12. Sweden 10
  13. Netherlands 10
  14. Israel 10
  15. South Korea 8

# What kind of organisations CNAs are

CNA types as listed by the CVE Program (one CNA can have several).

  1. Vendor 459
  2. Open Source 152
  3. Researcher 126
  4. Hosted Service 41
  5. CERT 22
  6. Bug Bounty Provider 20
  7. Consortium 3
  8. N/A 2
  9. AI Researcher (Frontier AI Researcher CVE Numbering Authorities (CNAs) Pilot) 2

Vendors

# Vendors with the most CVEs, last 12 months

25 566 vendor names appear in CVE records (after merging obvious variants like 'Inc.' and letter case).

  1. Linux 9 344
  2. Microsoft 5 670
  3. Google 4 845
  4. Oracle Corporation 4 155
  5. IBM 1 911
  6. Apache Software Foundation 1 517
  7. Red Hat 1 442
  8. Adobe 1 269
  9. Apple 1 259
  10. Mozilla 986
  11. Dell 711
  12. OpenClaw 672
  13. SourceCodester 469
  14. code-projects 448
  15. NVIDIA 432

# Vendors with the most CVEs, all time

  1. Linux 18 408
  2. Microsoft 14 266
  3. Google 9 109
  4. Oracle Corporation 9 094
  5. IBM 6 576
  6. Adobe 5 219
  7. Apple 4 637
  8. Cisco 3 442
  9. Apache Software Foundation 3 021
  10. Qualcomm, Inc. 2 991
  11. Red Hat 2 609
  12. Mozilla 2 561
  13. SourceCodester 2 065
  14. Dell 1 945
  15. Siemens 1 854

# Vendors with the most exploited CVEs

CVEs on any 'exploited' list, by vendor named in the CVE record.

Researchers

# Most credited researchers, all time

25 620 distinct names are credited in CVE records. 58% of them appear once; the top 1% of names account for 38% of credits.

WPScan4 7392 36427705 Apr 202116 Nov 2026
VulDB CNA Team2 7472 715161028 Apr 202315 Nov 2026
João Pedro S Alcântara (Kinorth) | Patchstack Bug Bounty Program1 0564367309 Jul 202423 Oct 2026
SOPROBRO | Patchstack Bug Bounty Program7111305 Oct 20245 Jan 2026
Tran Nguyen Bao Khanh (VCI - VNPT Cyber Immunity) | Patchstack Bug Bounty Program69749689024 Jan 202515 Nov 2026
George Chen62662676019 May 202616 Nov 2026
Nabil Irawan | Patchstack Bug Bounty Program6242746024 Feb 202519 Aug 2026
Francesco Carlucci56511608 Nov 20219 Nov 2026
VulDB GitHub Commit Analyzer51015002 Nov 20229 Nov 2026
Rafie Muhammad (Patchstack)502091022 Nov 202228 Aug 2025
Bonds | Patchstack Bug Bounty Program476322101017 Sep 202430 Oct 2026
István Márton471376014 Feb 202327 Nov 2025
Nguyen Xuan Chien | Patchstack Bug Bounty Program435314028 Feb 20242 Jun 2026
Dmitrii Ignatyev4191080030 Aug 20235 Nov 2026
Krzysztof Zając418230029 Nov 202116 Aug 2026
Mika | Patchstack Bug Bounty Program4031327010 Apr 202417 Jun 2026
Mat Powell of Trend Micro Zero Day Initiative3803003 Jun 201919 Dec 2025
Wordfence PRISM3723725023 Jul 202613 Nov 2026
VulnCheck37137149018 Dec 202526 Oct 2026
Peter Thaleikis36218407 Mar 202431 Oct 2026
Muhammad Yudha - DJ | Patchstack Bug Bounty Program360710024 Jan 20258 Oct 2026
Muhammad Yudha - DJ353172301 Oct 202410 Oct 2026
hieuPenguinnn35235229011 Oct 202616 Nov 2026
Bob Matyas34883019 Jun 20232 Sep 2026
Lucio Sá33812003 Jan 202410 Jul 2026
Lana Codes33501017 Jul 202216 Jan 2024
SSL_Seven_Security Lab_WangZhiQiang_XiaoZiLong (VulDB User)330170015 Jan 202320 Sep 2026
Greg Knaddison (greggles)32925514131 Mar 202530 Oct 2026
Phat RiO | Patchstack Bug Bounty Program3272545807 Feb 202522 Oct 2026
Rafael Pedrero327367309 Mar 202221 Apr 2026
Source: CVE List V5. Names exactly as credited in the CVE record (case and spacing merged). A name can be a person, a team, a company or a tool.

Credit

# Most credited, last 12 months

# How often CVEs credit a finder

Share of each year's CVEs whose record credits anyone.

0%20%40%20172019202120232025CVEs that credit …

# Credited names per year

05k10k15k2017201820192020202120222023202420252026

# Credit roles

The role a CVE record gives each credit (CVE JSON 5 'type').

  1. finder 68 572
  2. reporter 22 659
  3. unspecified 13 141
  4. coordinator 10 705
  5. remediation developer 3 972
  6. analyst 2 603
  7. tool 813
  8. remediation reviewer 652
  9. sponsor 197
  10. other 116
  11. remediation verifier 24

Zero Day Initiative

# Zero Day Initiative advisories per year

ZDI buys vulnerability reports from researchers and publishes advisories after disclosure.

05001k1.5k2k20052007200920112013201520172019202120232025

# ZDI advisories by vendor, since 2020

  1. Adobe 1 017
  2. Microsoft 922
  3. Autodesk 495
  4. Foxit 419
  5. Siemens 384
  6. Apple 359
  7. Delta Electronics 283
  8. Advantech 282
  9. PDF-XChange 280
  10. Trend Micro 274
  11. D-Link 260
  12. Oracle 219
  13. Bentley 208
  14. Cisco 206
  15. SAP 198

Weaknesses

What kind of bugs: weaknesses and techniques

CWE names the kind of mistake behind a vulnerability; MITRE ATT&CK names what an attacker gains by exploiting it. Each CWE links to its page with every CVE that names it.

Weaknesses on its own page →

The most common

# Most common weaknesses, last 12 months

The most common is CWE-79: Improper Neutralization of Input During Web Page Generation. 6% of the year's CVEs name no CWE.

# Weaknesses behind exploited CVEs

Rising and falling

# Rising and falling weaknesses

The year's top 25 against the 12 months before.

1CWE-79Improper Neutralization of Input During Web Page Generation9 559+13%=
2CWE-862Missing Authorization5 971+159%▲ 2
3CWE-284Improper Access Control4 813+296%▲ 5
4CWE-89Improper Neutralization of Special Elements used in an SQL Command4 678+20%▼ 2
5CWE-416Use After Free3 694+214%▲ 4
6CWE-22Improper Limitation of a Pathname to a Restricted Directory3 377+231%▲ 6
7CWE-125Out-of-bounds Read2 816+158%▲ 3
8CWE-200Exposure of Sensitive Information to an Unauthorized Actor2 667+235%▲ 10
9CWE-863Incorrect Authorization2 626+448%▲ 16
10CWE-639Authorization Bypass Through User-Controlled Key2 503+617%▲ 22
11CWE-78Improper Neutralization of Special Elements used in an OS Command2 417+188%▲ 3
12CWE-918Server-Side Request Forgery2 398+353%▲ 12
13CWE-122Heap-based Buffer Overflow2 306+316%▲ 10
14CWE-20Improper Input Validation2 271+250%▲ 6
15CWE-94Improper Control of Generation of Code2 261+63%▼ 9
16CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component2 238−7%▼ 13
17CWE-787Out-of-bounds Write2 233+153%▼ 4
18CWE-306Missing Authentication for Critical Functionality2 103+413%▲ 11
19CWE-400Uncontrolled Resource Consumption1 643+270%▲ 7
20CWE-121Stack-based Buffer Overflow1 627+95%▼ 5
21CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer1 498+38%▼ 10
22CWE-502Deserialization of Untrusted Data1 495+140%▼ 1
23CWE-269Improper Privilege Management1 490+354%▲ 11
24CWE-287Improper Authentication1 487+314%▲ 7
25CWE-352Cross-Site Request Forgery1 485−23%▼ 20

Families over time

# Three families of weakness over time

Share of each year's CVEs (among those naming a CWE) in each family. A CVE can be in more than one.

  • Injection (XSS, SQL, command, code)
  • Memory safety (overflow, use-after-free, …)
  • Access control and authentication
0%10%20%30%40%20122014201620182020202220242026Injection (XSS, S…Memory safety (ov…Access control an…

# The same families among exploited CVEs

By year of first 'exploited' listing.

  • Injection
  • Memory safety
  • Access control
0%10%20%30%40%20222023202420252026InjectionMemory safetyAccess control

ATT&CK

# ATT&CK techniques that exploited CVEs enable

MITRE Center for Threat-Informed Defense mapping of KEV entries to ATT&CK.

  1. T1059: Command and Scripting Interpreter 170
  2. T1190: Exploit Public-Facing Application 157
  3. T1068: Exploitation for Privilege Escalation 69
  4. T1078: Valid Accounts 46
  5. T1005: Data from Local System 46
  6. T1203: Exploitation for Client Execution 43
  7. T1105: Ingress Tool Transfer 35
  8. T1204.002: Malicious File 33
  9. T1505.003: Web Shell 26
  10. T1133: External Remote Services 25
  11. T1189: Drive-by Compromise 21
  12. T1496: Resource Hijacking 19
  13. T1055: Process Injection 19
  14. T1003: OS Credential Dumping 18
  15. T1574: Hijack Execution Flow 16

# ATT&CK tactics

  1. execution 278
  2. initial-access 264
  3. privilege-escalation 135
  4. persistence 122
  5. stealth 111
  6. collection 65
  7. impact 61
  8. credential-access 56
  9. command-and-control 51
  10. discovery 41
  11. exfiltration 24
  12. lateral-movement 24
  13. resource-development 17
  14. defense-impairment 11
  15. defense-evasion 5

Records

How good the records are, and what NVD does with them

A CVE record is only as useful as what is in it: a severity, a weakness, the affected versions. CNAs write the record; CISA and NIST's NVD add to it. This is how complete records are and how far behind the enrichment runs.

Waiting for NVD analysis
18 172
Deferred by NVD
63 265
Analysed, last 12 months
44%

Records on its own page →

NVD

# What NVD did with each month's CVEs

18 172 CVEs are waiting for NVD analysis and 63 265 are deferred. Of the last 12 months' CVEs, NVD has analysed 44%.

  • Analysed
  • Modified after analysis
  • Deferred (will not be analysed)
  • Waiting
  • Other or not in NVD
05k10k15k20k2022Aug ’22Mar ’23Oct ’23May ’24Dec ’24Jul ’25Feb ’26Sep ’26

Completeness

# How complete CNA records are

Share of each year's CVE records in which the CNA itself supplied each field. Missing fields are what NVD and CISA fill in, when they can.

  • Has a CVSS score
  • Names a weakness (CWE)
  • Lists affected versions
  • Two or more references
0%25%50%75%100%20172019202120232025Has a CVSS scoreNames a weakness …Lists affected ve…Two or more refer…

# Who scored the CVE

The first available CVSS score, in this order: the CNA's, CISA's, NVD's.

  • The CNA
  • CISA (ADP)
  • NVD only
  • Nobody
0%25%50%75%100%2017201820192020202120222023202420252026

Scores

# CNA score minus NVD score

Where both scored (since 2020, 80 816 CVEs), they agree exactly 25% of the time. NVD is at least 2 points higher in 21% of cases; the CNA in 6%.

010k20k4.2%NVD 4+ higher5.3%NVD 3–411%NVD 2–311%NVD 1–214%NVD 0.05–125%equal9.4%CNA 0.05–113%CNA 1–24.7%CNA 2–31.4%CNA 3–40.4%CNA 4+ higher

# CISA's exploitation verdicts

SSVC 'Exploitation' as recorded by CISA: none, proof of concept, or active.

050k100k150k200knonepocactive

CISA enrichment

# CISA's enrichment (Vulnrichment)

Share of each month's CVEs carrying CISA's ADP container, and an SSVC exploitation decision.

  • CISA enrichment present
  • CISA SSVC decision present
0%25%50%75%100%2024Jun ’24Nov ’24Apr ’25Sep ’25Feb ’26Jul ’26CISA enrichment p…CISA SSVC decisio…

Open source

Package ecosystems, malicious packages and distribution fixes

OSV merges the advisories of every open-source ecosystem: GitHub's, PyPA's, Go's, RustSec's, and the Linux distributions'. It also records packages published to attack, which are not vulnerabilities at all.

Malicious packages recorded
241 648
Linux kernel share of CVEs, last year
8.9%
Median days, CVE to OSV advisory
0

Open source on its own page →

Ecosystems

# Open-source advisories per year, by ecosystem

Security advisories (GitHub, PyPA, Go, RustSec and others, merged by OSV) for packages in the main language ecosystems. Malicious packages excluded.

  • npm
  • PyPI
  • Maven
  • Go
  • Packagist
  • crates.io
  • NuGet
  • RubyGems
05k10k15k20k201520172019202120232025

# Ecosystems at a glance

PyPI14 2767 03613 94889%12 034
Go9 7554 7949 06988%20
npm7 7403 5896 66980%224 100
Packagist7 3001 8946 44088%1
Maven7 1331 1157 03784%2
crates.io2 9991 0861 80876%25
NuGet1 1754401 11896%782
RubyGems1 1422461 09794%4 321
Hex43639343697%0
GitHub Actions63254894%0
Pub12211100%0

Malicious packages

# Malicious packages reported per month

241 648 malicious packages are recorded in OSV, 93% of them on npm. These are not bugs: they are packages published to steal or attack.

  • npm
  • PyPI
  • Other ecosystems
050k100k150k2022Nov ’22Jun ’232024Aug ’24Mar ’25Oct ’25May ’26

Packages

# Packages with the most advisories, last 12 months

  1. openclaw 591
  2. open-webui 300
  3. praisonai 218
  4. github.com/siyuan-note/siyuan/kernel 216
  5. github.com/mattermost/mattermost-server 210
  6. tensorflow 185
  7. vllm 155
  8. code.gitea.io/gitea 153
  9. Magick.NET-Q16-AnyCPU 152
  10. Magick.NET-Q16-HDRI-AnyCPU 152
  11. Magick.NET-Q8-AnyCPU 152
  12. Magick.NET-Q16-HDRI-x86 151
  13. Magick.NET-Q8-x86 150
  14. Magick.NET-Q16-x86 150
  15. Magick.NET-Q16-arm64 148

Linux distributions

# Days from CVE publication to the first fixed distro advisory

CVEs published since September 2024 that Debian, Ubuntu or Red Hat later shipped a fix for, through a security advisory in OSV.

Debian28 3110500
Ubuntu17 0890330
Red Hat7 700213123
Sources: OSV.dev, CVE List V5. Measured to the first advisory with a fixed version in that distribution's OSV data. Negative: the distribution published before the CVE did (coordinated disclosure). Red Hat data in OSV starts in August 2024.

# Distribution of days to a distro fix

  • Before publication
  • Same day
  • After
020k40k3.1%> 1 mo before0.9%2–30 d before0.2%1 d before82%same day4.4%1–7 d3.2%1–4 wk3.5%1–3 mo1.5%3–6 mo0.9%6–12 mo0.1%> 1 yr

The kernel

# The Linux kernel, a CNA since 2024

The kernel team assigns a CVE to most fixes that could matter: 18 245 so far, 9% of all CVEs in the last 12 months.

01k2kFeb ’24Jun ’24Oct ’24Feb ’25Jun ’25Oct ’25Feb ’26Jun ’26Oct ’26

Research

Papers, conferences and bug bounties

Security research beyond CVE records: what is written on arXiv and presented at the top four academic security conferences, which CVEs papers talk about, and what bug-bounty programmes choose to disclose.

Research on its own page →

Papers

# Security papers on arXiv per year

7 912 papers in arXiv's Cryptography and Security category (cs.CR) in 2025, +21% on 2024.

02.5k5k7.5k10k2007200920112013201520172019202120232025
Source: arXiv cs.CR. Submissions with cs.CR as a category (primary or cross-listed).

# Papers at the 'big four' security conferences

1 299 papers at the four top academic security conferences in 2025; 1 237 in 2024.

  • IEEE S&P
  • USENIX Security
  • ACM CCS
  • NDSS
05001k1.5k20052007200920112013201520172019202120232025

# Most prolific authors at the big four, last five years

  1. Qi Li 0002 71
  2. Haixin Duan 61
  3. Yang Zhang 0016 58
  4. Min Yang 0002 56
  5. Xiapu Luo 53
  6. Michael Backes 0001 50
  7. Wenyuan Xu 0001 48
  8. Kui Ren 0001 47
  9. Shouling Ji 45
  10. Chao Zhang 0008 42
  11. Ahmad-Reza Sadeghi 41
  12. Ke Xu 0002 40
  13. Minhui Xue 0001 40
  14. Zhiqiang Lin 0001 39
  15. XiaoFeng Wang 0001 37

# Papers naming CVEs, per year

05101520201320172019202120232025

CVEs in papers

# CVEs most often named in papers

40 cs.CR papers name at least one CVE in their abstract.

CVE-2025-327112noM365 Copilot Information Disclosure Vulnerability
CVE-2024-258251noFydeOS for PC 17.1 R114, FydeOS for VMware 17.0 R114, FydeOS for You 17.1 R114, and OpenFyde R114 were discove
CVE-2024-416231noAn issue in D3D Security D3D IP Camera (D8801) v.V9.1.17.1.4-20180428 allows a local attacker to execute arbit
CVE-2026-62971noUse after free in Proxy in Google Chrome prior to 147.0.7727.101 allowed an attacker in a privileged network p
CVE-2023-508681noThe Closest Encloser Proof aspect of the DNS protocol (in RFC 5155 when RFC 9276 guidance is skipped) allows r
CVE-2017-56381YesThe Jakarta Multipart parser in Apache Struts 2 2.3.x before 2.3.32 and 2.5.x before 2.5.10.1 has incorrect ex
CVE-2019-199261nomultiSelect in select.c in SQLite 3.30.1 mishandles certain errors during parsing, as demonstrated by errors f
CVE-2024-425311noEzviz Internet PT Camera CS-CV246 D15655150 allows an unauthenticated host to access its live video stream by
CVE-2020-158021noDevices supporting Bluetooth before 5.1 may allow man-in-the-middle attacks, aka BLURtooth. Cross Transport Ke
CVE-2023-385451noThis flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass a
CVE-2025-60211noLibxml2: integer overflow in xmlbuildqname() leads to stack buffer overflow in libxml2
CVE-2026-252531noOpenClaw (aka clawdbot or Moltbot) before 2026.1.29 obtains a gatewayUrl value from a query string and automat
CVE-2022-464801noIncorrect Session Management and Credential Re-use in the Bluetooth LE stack of the Ultraloq UL3 2nd Gen Smart
CVE-2025-565381––
CVE-2026-52801noUse after free in WebCodecs in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to execute arbi
CVE-2021-338131noAn XXE issue in SAXBuilder in JDOM through 2.0.6 allows attackers to cause a denial of service via a crafted H
CVE-2023-205701noInsufficient verification of data authenticity in the configuration state machine may allow a local attacker t
CVE-2025-692481nofree5GC has Array Index Out of Bounds in AMF Leading to Denial of Service
CVE-2021-417731YesPath traversal and file disclosure vulnerability in Apache HTTP Server 2.4.49
CVE-2024-370181noThe OpenDaylight 0.15.3 controller allows topology poisoning via API requests because an application can manip

Bug bounties

# HackerOne: publicly disclosed reports per year

12 759 reports that programmes chose to disclose publicly. Disclosed reports are a small, self-selected share of all reports.

  • Disclosed reports
  • With a bounty
05001k1.5k2k2013201520172019202120232025Disclosed reportsWith a bounty

# Bounties on disclosed reports (USD)

2 275 disclosed reports show a bounty; the median was $500, the largest $50 000.

02004006008004.4%$0–10016%$100–25012%$250–50029%$500–1k21%$1k–2.5k9.2%$2.5k–5k4.5%$5k–10k3.5%$10k–25k0.5%> $25k

# Programmes with the most disclosed reports

  1. U.S. Dept Of Defense 896
  2. Internet Bug Bounty 817
  3. curl 688
  4. Nextcloud 623
  5. HackerOne 614
  6. Shopify 469
  7. Node.js third-party modules 307
  8. GitLab 258
  9. X / xAI 250
  10. Uber 239
  11. VK.com 172
  12. Node.js 170
  13. Automattic 166
  14. Weblate 163
  15. shopify-scripts 161

# Weaknesses in disclosed reports

  1. Information Disclosure 1 193
  2. Cross-site Scripting (XSS) - Generic 744
  3. Violation of Secure Design Principles 716
  4. Improper Access Control - Generic 706
  5. Improper Authentication - Generic 672
  6. Cross-site Scripting (XSS) - Reflected 523
  7. Uncontrolled Resource Consumption 510
  8. Cross-site Scripting (XSS) - Stored 475
  9. Cross-Site Request Forgery (CSRF) 422
  10. Privilege Escalation 375
  11. Business Logic Errors 356
  12. Memory Corruption - Generic 308
  13. Code Injection 299
  14. Insecure Direct Object Reference (IDOR) 292
  15. Open Redirect 273

# Most disclosed hackers

Reporters by number of publicly disclosed reports.

  1. giant_anteater 94
  2. geeknik 80
  3. sp1d3rs 69
  4. jobert 68
  5. nyymi 67
  6. ooooooo_q 55
  7. guido 50
  8. netfuzzer 48
  9. ryat 47
  10. japz 44
  11. bl4de 43
  12. bobrov 40
  13. chalker 37
  14. haxta4ok00 35
  15. rtod 35