What is cve

Last updated: April 1, 2026

Quick Answer: CVE (Common Vulnerabilities and Exposures) is a standardized system that identifies, catalogs, and tracks security vulnerabilities in software and systems, assigning each vulnerability a unique identifier to help organizations manage cybersecurity risks.

Key Facts

Overview

CVE stands for Common Vulnerabilities and Exposures, a comprehensive system for identifying and organizing security vulnerabilities in software and hardware. Think of CVE as a standardized dictionary of security flaws—it provides a common language that allows security professionals, vendors, and organizations to communicate about specific security problems. By assigning unique identifiers to vulnerabilities, CVE enables better coordination in addressing cybersecurity threats.

History and Purpose

The CVE system was created in 1999 and is maintained by the MITRE Corporation, with funding and oversight from the U.S. Cybersecurity and Infrastructure Security Agency (CISA). The primary purpose of CVE is to standardize the naming and identification of security vulnerabilities. Before CVE, different organizations used different names and classification systems for the same vulnerability, making it difficult to track and coordinate responses. CVE solved this problem by establishing a single, authoritative source for vulnerability information.

How CVE IDs Work

Each vulnerability registered in the CVE system receives a unique identifier called a CVE ID. These IDs follow a standardized format: CVE-YYYY-NNNN, where YYYY is the year the vulnerability was reported, and NNNN is a sequential number. For example, CVE-2023-12345 refers to a specific vulnerability discovered in 2023. This standardized naming convention makes it easy to reference vulnerabilities in reports, databases, and communications. When a security researcher discovers a vulnerability, they can request a CVE ID from designated CVE Numbering Authorities (CNAs), which then becomes the official identifier for that vulnerability.

The CVE Database

The official CVE list is publicly accessible through the National Vulnerability Database (NVD), maintained by the National Institute of Standards and Technology (NIST). This database contains detailed information about each CVE, including:

Why CVE Matters for Cybersecurity

CVE provides the foundation for modern cybersecurity management. Organizations use CVE identifiers to prioritize security updates based on which vulnerabilities might affect their systems. Software vendors use CVE to track bugs and release patches systematically. Security researchers use CVE to communicate about threats and share discoveries. Government agencies and compliance frameworks (like HIPAA and PCI-DSS) reference CVE IDs when establishing security requirements. The standardization provided by CVE significantly improves the speed and effectiveness of the global response to security threats.

CVE vs. CVSS Severity Ratings

It's important to note that CVE itself only identifies the vulnerability; it doesn't rate its severity. That's where CVSS (Common Vulnerability Scoring System) comes in. While CVE assigns an ID to a vulnerability, CVSS provides a numerical score (0-10) indicating how serious the vulnerability is. A vulnerability might have a low CVSS score if it's difficult to exploit, or a high score if it poses an immediate threat to many systems.

Related Questions

What is CVSS and how does it differ from CVE?

CVSS (Common Vulnerability Scoring System) rates the severity of a vulnerability on a 0-10 scale, while CVE is the identifier and catalog system. CVE tells you which vulnerability exists; CVSS tells you how serious it is.

How often are new CVE IDs assigned?

New CVE IDs are assigned continuously as vulnerabilities are discovered. Thousands of new CVEs are assigned annually across all software types and platforms worldwide.

Can anyone request a CVE ID?

Security researchers and organizations can request CVE IDs through designated CVE Numbering Authorities (CNAs), though the process requires verification and documentation of the vulnerability.

Sources

  1. CVE Official Website Public Domain
  2. NIST Guide to Enterprise Patch Management Public Domain