Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A CVE (Common Vulnerabilities and Exposures) identifier is a unique reference for a publicly disclosed vulnerability, giving vendors, scanners, and defenders one shared name.
What Is a CVE?
A CVE (Common Vulnerabilities and Exposures) identifier is a unique reference number assigned to a publicly disclosed security vulnerability, such as CVE-2021-44228 for Log4Shell. It gives vendors, researchers, scanners, and defenders a common name for the same flaw, so a patch advisory, a scanner finding, and a threat intelligence report can all be linked together. A CVE is a label and a short description, not a severity score or a fix.
The CVE Program was launched by MITRE in 1999 and is sponsored by the US Cybersecurity and Infrastructure Security Agency (CISA). MITRE operates it under contract, but most identifiers are now assigned by CVE Numbering Authorities (CNAs): more than 400 organisations, including Microsoft, Google, Red Hat, Cisco, national CERTs, and bug bounty platforms, each permitted to issue IDs for vulnerabilities within its own scope. Where no CNA covers a product, a “CNA of last resort” such as MITRE handles the request.
The format is CVE-YYYY-NNNN: the year the ID was reserved, followed by a sequence number of four or more digits. The year does not always match the disclosure date, because IDs are often reserved months before a flaw becomes public.
Downstream, the US National Vulnerability Database (NVD), run by NIST, enriches records with CVSS scores and CPE product identifiers. A large enrichment backlog that built up from early 2024 showed how much of the industry depended on that single service, and encouraged wider use of CNA-supplied scores and other sources such as ENISA’s European Vulnerability Database, launched in 2025.
A CVE ID tells you that a flaw exists and roughly where. It does not tell you how bad it is in your environment, whether it is being exploited, or whether you are affected at all. For that you need additional context:
Not every vulnerability gets a CVE. Bugs in your own custom applications, flaws in SaaS platforms fixed on the provider’s side, and misconfigurations generally do not. That is why a clean scan against known CVEs is not the same as a secure system, and why penetration testing still finds issues that scanners miss.
| CVE | Name | Why it mattered |
|---|---|---|
| CVE-2014-0160 | Heartbleed | OpenSSL memory over-read exposing private keys and session data on a large share of web servers |
| CVE-2017-0144 | EternalBlue | SMBv1 flaw behind the WannaCry and NotPetya outbreaks |
| CVE-2021-44228 | Log4Shell | Remote code execution in the ubiquitous Log4j library, rated CVSS 10.0 |
| CVE-2023-34362 | MOVEit Transfer | SQL injection exploited by the Cl0p group in a mass data-theft campaign that reached the BBC, British Airways, and Boots through payroll provider Zellis |
Each showed how quickly a published flaw turns into mass exploitation once a working exploit is available. Log4Shell and MOVEit were both exploited as zero-days, before most organisations even knew they were exposed.
In April 2025 MITRE warned that its contract to run the CVE Program was about to expire. CISA extended it at the last minute, but the episode exposed how much global vulnerability management relies on a single US-funded service. It prompted the creation of the CVE Foundation and renewed interest in more internationally governed alternatives, a debate that continues.
For security teams, CVEs are most useful as a join key. Map them to your asset inventory, enrich them with exploitation data, and track each one from detection to remediation with an owner and a deadline. Subscribing to vendor advisories and the NCSC’s alerts helps you hear about the critical ones early.
Tracking which CVEs affect which assets, and fixing the dangerous ones first, is a continuous job. Our vulnerability management solutions help organisations do it systematically.
First contact the vendor, because many vendors are CNAs and will assign an ID as part of fixing the issue. If the vendor is not a CNA, check the CNA list on the CVE website for one whose scope covers the product, such as a platform for open-source projects. If no CNA applies, submit a request to the CNA of last resort through the CVE Program’s web form.
Not necessarily. Most CVEs are published alongside a vendor fix under coordinated disclosure, but some are published before a patch exists, for products that are end of life, or with only a workaround. Always check the vendor advisory. If no fix is available, reduce exposure with compensating controls such as network restrictions, disabling the affected feature, or increased monitoring.
The year in a CVE ID reflects when the identifier was reserved, not when the vulnerability was disclosed or fixed. CNAs often reserve blocks of IDs in advance and assign them to issues that take months to investigate and patch. A CVE from an earlier year appearing in a new advisory is normal and does not mean the flaw is old news.
No. CVEs range from trivial issues that require local access and unusual conditions to critical remote code execution flaws. Only a small fraction are ever exploited in the wild. Prioritise using CVSS together with exploitation evidence such as the CISA KEV catalogue or EPSS scores, and above all your own context: whether the vulnerable system exists in your estate and is exposed.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.