{"canonical_url":"https://engineer.company/glossary/cve/","content_markdown":"# CVE\n\n## What it is\n\nCVE, short for Common Vulnerabilities and Exposures, is the public catalogue of\npublicly disclosed cybersecurity vulnerabilities, with one CVE Record for each.\nThe CVE Program describes its mission as identifying, defining and cataloguing\nthose vulnerabilities, so that two people or two tools can refer to a flaw and\nknow they mean the same one. The word is used for the programme, for the list,\nand loosely for a single entry, as in \"that library has two open CVEs\".\n\nEvery record carries a CVE ID. The format is the prefix `CVE`, a four-digit year\nand a sequence number of four or more digits, so `CVE-1999-0067`,\n`CVE-2019-12345` and `CVE-2021-7654321` are all valid; the programme sets no\nupper limit on the length of the sequence number. The year is the year the ID\nwas reserved or the year the vulnerability was made public. In the programme's\nown words, \"the year portion is not used to indicate when the vulnerability was\ndiscovered\".\n\nIDs are not handed out by one central desk. CVE Numbering Authorities, or CNAs,\nare vendors, researchers, open-source projects, emergency response teams, online\nservice operators, bug bounty providers and consortia that the programme has\nauthorised to assign IDs and publish records, each within its own scope. Every\nCVE Record is added by a CNA, there is no fee or contract to sign to become one,\nand since 2016 the programme has been actively adding more of them.\n\nA record moves through three states. It starts as Reserved, when a CNA has taken\nan ID that the parties involved use to coordinate early work on the\nvulnerability ahead of disclosure. It becomes Published once the CNA has filled\nin at least the ID, a short description, the affected products and versions, and\na public reference. If the ID should no longer be used, it becomes Rejected, and\nthe record stays on the list so that anyone holding the ID can see that it is\nvoid.\n\nThe idea dates from 1999. Two MITRE engineers, David E. Mann and Steven M.\nChristey, presented the concept as a white paper at a workshop at Purdue\nUniversity in January 1999, and the list went public in September 1999 with 321\nrecords.\n\n## Why it matters\n\nA vulnerability report is only useful if the people who read it can tell whether\nit is the same problem as the one in another report. A CVE ID settles that: two\nadvisories, a scanner finding and a ticket that carry the same ID are about the\nsame flaw. Numerous major operating system vendors put CVE IDs into their\nadvisories so that everyone has the ID from the moment a problem is announced,\nand security products and services around the world build CVE Records into what\nthey report.\n\nOther services are built on the list rather than beside it. The US National\nVulnerability Database, launched by NIST in 2005, is a separate programme that\nbuilds on CVE Records and adds its own analysis to each one. CISA's Known\nExploited Vulnerabilities (KEV) catalogue lists flaws that attackers have been\nseen to use. Each entry names its CVE ID and links to the corresponding record.\n\nThe most useful thing to know about CVE is what it is not. Severity is measured\nseparately by CVSS, the Common Vulnerability Scoring System, a standard run by\nFIRST, a US-based non-profit whose mission is to help computer security response\nteams around the world. CVSS version 4.0 rates a vulnerability from 0 to 10\nusing the Base, Threat, Environmental and Supplemental groups of metrics, and\nmaps the number onto None, Low, Medium, High and Critical, with Critical running\nfrom 9.0 to 10.0. The CVE Record Format lets a CNA include a CVSS score in its\nrecord, but the score belongs to CVSS, not to the ID: one flaw can carry\ndifferent scores from different publishers, or none.\n\nNor is it a weakness class. The Common Weakness Enumeration, CWE, is a\ncommunity-developed list of weaknesses: conditions in software, firmware,\nhardware or a service that can, in the right circumstances, let a vulnerability\nin. The CVE Program describes CWEs as the root causes of CVE Records. A CVE\nnames one flaw in one product; a CWE names the type of error behind it. SQL\ninjection, for instance, is the weakness CWE-89, and every product found to have\nmade that mistake gets a CVE ID of its own.\n\n## What it looks like in practice\n\nShellshock, the 2014 flaw in Bash, shows all three systems side by side. cve.org\ndisplays its records in the CVE Record Format, a JSON format, and the top of\nthis one reads as follows (fields trimmed and reordered):\n\n```json\n{\n  \"dataType\": \"CVE_RECORD\",\n  \"dataVersion\": \"5.1\",\n  \"cveMetadata\": {\n    \"cveId\": \"CVE-2014-6271\",\n    \"assignerShortName\": \"debian\",\n    \"state\": \"PUBLISHED\",\n    \"dateReserved\": \"2014-09-09T00:00:00.000Z\",\n    \"datePublished\": \"2014-09-24T18:00:00.000Z\",\n    \"dateUpdated\": \"2025-10-22T00:05:36.342Z\"\n  }\n}\n```\n\nDebian, acting as CNA, reserved the ID on 9 September 2014 and published the\nrecord fifteen days later. Its description says that Bash up to version 4.3\nprocesses text that trails a function definition in the value of an environment\nvariable, which lets a remote attacker run arbitrary code through a crafted\nenvironment. It also records that the first fix was incorrect and that the part\nstill open after it received an ID of its own, CVE-2014-7169. Teams that patched\nonce and stopped were still exposed.\n\nThe record then holds containers from three different sources. The CNA container\nholds Debian's description and references. The CVE Program Container adds\nreferences of its own. A third, from an Authorized Data Publisher and titled\nCISA ADP Vulnrichment, adds the material that the CVE ID alone does not carry:\n\n```json\n{\n  \"cvssV3_1\": {\n    \"version\": \"3.1\",\n    \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\",\n    \"baseScore\": 9.8,\n    \"baseSeverity\": \"CRITICAL\"\n  }\n}\n```\n\nThe vector string spells out the reasoning behind 9.8: an attack over the\nnetwork, of low complexity, needing no privileges and no user interaction, with\nhigh impact on confidentiality, integrity and availability. The same container\nmaps the flaw to CWE-78, the weakness class for operating-system command\ninjection, and records that on 28 January 2022 CISA added it to the KEV\ncatalogue. One record therefore holds an ID from the CVE Program, a score from a\nCVSS version that FIRST publishes, and a weakness class from CWE, each from a\ndifferent source and each answering a different question.\n\nDay to day, CVE IDs matter less as reading matter than as keys. Our\n[security page](/security/) describes the routine: the parts each system is\nbuilt from are listed, and the list is compared with published advisories\ninstead of being trusted because it worked before. The CVE ID is what lets a\nfinding from that check be traced back to the advisory, and forward to the\nupgrade that closes it.\n\n## Where it goes wrong\n\n**Reading the score as the risk.** When nobody supplies Threat or Environmental\nvalues, the CVSS 4.0 specification fills them with defaults that assume the\nworst, and it notes that NVD and product maintainers usually publish only the\nBase score. A 9.8 on a component that is unreachable from outside is not a 9.8\nfor you. Label scores the way the specification asks, CVSS-B for Base only and\nCVSS-BTE when Threat and Environmental values were applied, and add the\nEnvironmental values for your own systems before ranking the work.\n\n**Mixing up CVE, CVSS and CWE.** \"A CVE of 9.8\" mixes an identifier with a\nscore, and \"the SQL injection CVE\" mixes a flaw with a class of flaws. Keep the\nthree apart in tickets and reports: the ID from CVE, the score with its version\nfrom CVSS, and the root cause from CWE.\n\n**Quoting a number without its vector.** FIRST requires anyone who publishes\nCVSS data to publish its vector alongside the number, making the underlying\nchoices available for inspection. A bare number cannot be checked, compared\nacross CVSS versions or adjusted for your setting. Store the full vector,\nincluding the `CVSS:3.1/` or `CVSS:4.0/` prefix that names the version.\n\n**Reading the year as the discovery date.** The year in the ID is when the ID\nwas reserved or the flaw went public. A 2014 ID can describe code shipped in the\n1990s, and a flaw found in December may carry the next year's number. Use the\nrecord's `dateReserved` and `datePublished` fields for dates, never the ID.\n\n**Assuming four digits.** The sequence number has four or more digits with no\nupper bound, so a pattern such as `CVE-\\d{4}-\\d{4}` silently cuts longer IDs\nshort. Match `^CVE-[0-9]{4}-[0-9]{4,}$` instead, and treat the ID as a string,\nnot a number, so that leading zeros survive.\n\n**Treating a Rejected record as missing.** A Rejected ID stays on the list on\npurpose, to tell users it is void. Tooling that ignores it, or that counts it as\nan open finding, misleads in either direction. Read the `state` field and handle\n`REJECTED` explicitly.\n\n**Treating the record as finished.** The Shellshock record was last changed in\nOctober 2025, eleven years after it was published, and its KEV entry arrived in\nJanuary 2022. The CVSS specification uses its Threat group to account for\nchanges in a vulnerability's circumstances over time. Re-read the records behind\nany finding you have accepted rather than fixed, and do so on a schedule.\n\n**Stopping at the first fix.** Shellshock needed a second ID because the first\npatch left part of the flaw open. Read each record's description and references\nfor follow-up IDs, and close a finding only when every ID that names the\ncomponent is resolved.\n\n**Taking no CVE to mean no vulnerability.** CVE covers vulnerabilities that have\nbeen publicly disclosed and given an ID by a CNA within its scope. A flaw in\nyour own code has no CVE until someone reports and publishes it. Scanning\ndependencies against the list covers what others have found; your own code needs\nits own static analysis, review and testing.\n\n## Further reading\n\n- [CVE Program: Overview](https://www.cve.org/About/Overview)\n  — the mission, the CVE Record, and the partners who assign and publish them.\n- [CVE Program: Process](https://www.cve.org/About/Process)\n  — the ID format, the minimum content of a record, and its three states.\n- [CVE Program: Related Efforts](https://www.cve.org/About/RelatedEfforts)\n  — how NVD, CVSS, the KEV catalogue and CWE relate to CVE, and where they\n  differ.\n- [Common Vulnerability Scoring System v4.0: Specification Document](https://www.first.org/cvss/v4.0/specification-document)\n  — FIRST's metric groups, score labels and qualitative severity scale.\n- [CVE Record Format](https://github.com/CVEProject/cve-schema)\n  — the JSON definition of how a record is structured, in the version that\n  CVE Services uses.\n\n\n- [CVE Program: FAQs (archive)](https://www.cve.org/Resources/Media/Archives/OldWebsite/about/faqs.html)\n\n\u003chttps://engineer.company/glossary/cve/\u003e\n","date_modified":"2026-10-30T02:51:31Z","description":"How the CVE list gives each publicly disclosed vulnerability one ID, who assigns it, what a record holds, and why it is not a severity score.","formats":{"gemtext":"https://engineer.company/glossary/cve/index.gmi","gopher":"https://engineer.company/glossary/cve/gophermap","html":"https://engineer.company/glossary/cve/","json":"https://engineer.company/glossary/cve/index.json","markdown":"https://engineer.company/glossary/cve/index.md","pdf":"https://engineer.company/glossary/cve/index.pdf"},"kind":"page","language":"en","title":"What is CVE?","url":"https://engineer.company/glossary/cve/","version":1}