The CVE-2025 list

43,639 CVE-2025 records, searchable in one list

The year in a CVE identifier is usually the year the CVE Program assigned it, so CVE-2025 records kept appearing after 2025 ended. Search them by number, vendor or product, filter by severity and signal, and open each one on cve-security.com for its sources, detection content and remediation. The signals include a listing in the Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities (KEV) catalog and the Exploit Prediction Scoring System (EPSS) score, where a record carries one.

By publication month

CVE-2025 records by the month each record was published. CVE Numbering Authorities still publish records under identifiers assigned in 2025, and the 5,305 published since then sit together under After 2025. Each page lists its records and the share that carry a detection signal, exploit code or an actionable vendor fix.

Published after 2025

  1. After 20255,305

CISA KEV listings by month

The 189 CVE-2025 records CISA has added to the KEV catalog, counted by the month CISA listed each one. Every date on this chart is the CISA listing date, which can fall weeks or months after the record was published. The last column holds the 38 listings CISA has made since 2025 ended.

CISA listing month
Table view
CVE-2025 records CISA added to the KEV catalog, by CISA listing month
CISA listing monthListings
January 20256
February 20259
March 202517
April 202512
May 202515
June 202511
July 202515
August 20258
September 202513
October 202519
November 202510
December 202516
After 202538

Vendors

Most CVE-2025 records in CISA KEV

Counted by the vendor label CISA gives each KEV entry, which can name a company or a platform. Vendors tied at the cutoff share the last row.

#CISA vendor labelKEV-listed
1Microsoft30
2Apple11
3Fortinet9
4Google7
5Cisco6
6Android4
6Gladinet4
6Ivanti4
6Synacor4
1011 tied: Citrix, Craft CMS, Dassault Systèmes, Kentico, Linux, Oracle, Qualcomm, Samsung, SolarWinds, TeleMessage and VMware3 each

Most CVE-2025 records

Counted by the vendors each record names in its product data. The counts follow how vendors and CVE Numbering Authorities publish and how products are mapped, so they say nothing about how secure one vendor is compared with another. A record that names two vendors counts for each.

#VendorRecords
1Linux2,678
2Microsoft1,263
3Adobe830
4Apple706
5Debian662
6Google614
7Phpgurukul590
8IBM517
9Tenda480
10D-Link372

Vendor names lead to their pages on cve-security.com, which cover CVEs from every year.

Weakness classes

The 10 Common Weakness Enumeration (CWE) classes named by the most CVE-2025 records. 41,871 of the 43,639 records name at least one class, and a record can name several, so the rows overlap.

CWEWeaknessRecordsShare
CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')7,68917.6%
CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')3,8708.9%
CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')2,5715.9%
CWE-862Missing Authorization2,3705.4%
CWE-352Cross-Site Request Forgery (CSRF)1,7424.0%
CWE-94Improper Control of Generation of Code ('Code Injection')1,3153.0%
CWE-284Improper Access Control1,2152.8%
CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer1,1632.7%
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')1,0862.5%
CWE-787Out-of-bounds Write1,0562.4%

What the list holds

Records
Each row is a CVE-2025 identifier with a published record in the cve-security.com dataset, which reads the CVE Program's records and NVD. The 1,788 identifiers the CVE Program has rejected stay off the list; opening one on cve-security.com shows the rejection.
CVSS
The score is the primary CVSS assessment cve-security.com shows for the CVE. Beneath it sit the scorer (NVD, the CVE Numbering Authority that published the record, or CISA's Authorized Data Publisher enrichment) and the CVSS version. A record without an assessment shows no score.
EPSS
The estimate FIRST.org publishes of the probability that exploitation activity against the CVE is observed in the next 30 days, refreshed daily.
Exploitation
KEV marks a CVE that CISA lists as confirmed exploited. Reported exploited marks a CVE that another tracker reports as exploited while it remains outside CISA KEV, as KEV Watch™ lists it; the CVE page names the tracker and links its report.
Detection
A detection signal is public detection content this dataset holds: a Nuclei template, a Metasploit check module, an Emerging Threats rule or a Snort rule that works over the network. It says the content exists, and a given product or environment may still miss the exploitation.
Exploit code
A Metasploit exploit module, an Exploit-DB entry or a public proof-of-concept repository that this dataset holds. Exploit code shows that an attack can be built and reports no attack on its own.
Vendor fix
An actionable vendor fix is a fixed version or a vendor advisory this dataset holds. The remediation panel on the CVE page says which affected products it covers.
Rankings
The KEV vendor list counts the vendor label CISA gives each KEV entry. The record list counts the vendors named in each record's product data, and the weakness table the CWE classes each record names. Each figure comes from one of these sources, and no figure adds them together.
Data access
Each record's full detail is in the API and nightly download on cve-security.com, which take a free key.
Freshness
The list rebuilds each night from the cve-security.com dataset, which refreshes hourly, so the CVE page carries the current record.