Skip to content
ContentLora

    Tip: press / anywhere to search.

    Explainer

    The CVE program: how software vulnerabilities get their IDs

    The CVE program gives each publicly disclosed cybersecurity vulnerability a unique ID and record, so that vendors, defenders and tools know they are talking about the same flaw.[1][2] Records are published by partner organizations called CNAs, and volumes are soaring: 48,244 CVE Records were published in 2025 and 36,962 in the third quarter of 2026 alone, and NIST's vulnerability database now adds details only to prioritized ones.[3][4][5][6]

    Editor reviewedUpdated Explainer19 claims · 89% primaryCybersecurity
    Reading level: 1 passage differs; the rest is the same for everyone.

    What the CVE program does

    When a security flaw is found in software, people need a way to refer to it without confusion. The CVE program (Common Vulnerabilities and Exposures) catalogs publicly disclosed flaws and gives each one a single record with a unique ID.[1] IT staff and security tools use those IDs to make sure they are discussing the same problem and to coordinate fixes.[2]

    An ID has three parts: the prefix CVE, a year and a sequence number of four or more digits. The year records when the ID was reserved or the flaw made public, not when it was discovered.[7] A published record must include at least the ID, a short description, the affected products and versions, and references such as advisories.[8]

    How a vulnerability gets a CVE

    The program’s lifecycle runs from discovery to publication. Someone finds a flaw and reports it to the program, and an ID is requested and reserved for it.[9] While an ID is reserved, the people involved can coordinate a fix privately before the flaw is disclosed.[10] Once the minimum details are filled in, the responsible partner publishes the record.[9]

    Those partners are CVE Numbering Authorities (CNAs): software vendors, researchers, open-source projects, national CERTs, hosted services, bug bounty platforms and consortia, each allowed to assign IDs within its own scope. There is no fee or contract to join.[3] The program stresses that it is not run entirely by the MITRE Corporation, which operates it under contract.[11][12]

    Severity scores and the NVD

    A CVE record says what a flaw is, not how bad it is; the program lists the idea that it assigns severity scores as a myth.[11] Severity is instead commonly expressed with the Common Vulnerability Scoring System (CVSS), a standard maintained by the Forum of Incident Response and Security Teams (FIRST) and used by organizations worldwide. It turns a flaw’s main characteristics into a numerical score that maps to ratings from low to critical, and is now at version 4.0.[13]

    The US National Institute of Standards and Technology (NIST) runs the National Vulnerability Database (NVD), which adds details such as scores and lists of affected products to CVE records. On 15 April 2026 NIST said submissions had risen 263% between 2020 and 2025 and that it would now enrich only prioritized CVEs, starting with those on CISA’s Known Exploited Vulnerabilities (KEV) catalog, software used by the federal government and critical software. The rest are labelled “lowest priority”.[6] NIST said it had enriched nearly 42,000 CVEs in 2025, 45% more than in any earlier year, and still could not keep up.[14]

    The flood of new CVEs

    The CVE Program’s own figures show the growth. Partners published 48,244 CVE Records across the four quarters of 2025.[4] In 2026 the quarterly total climbed from 15,154 to 20,696 and then to 36,962 in the third quarter.[5] That single quarter is three-quarters of 2025’s full-year total.[4][5]

    Not every CVE is attacked. CISA’s KEV catalog lists only flaws with reliable evidence of exploitation in the wild, an assigned CVE ID and clear remediation guidance.[15] It held 1,769 entries in early November 2026.[16] US federal civilian agencies must fix catalogued flaws by set deadlines under Binding Operational Directive 22-01, and CISA suggests other organizations use the list as one input to prioritization.[17][18] Flaws exploited before any fix exists are covered in zero-day vulnerabilities.

    The 2025 funding scare

    The program depends on US government funding. In April 2025 MITRE warned that its contract to run the CVE program was expiring. CISA then said it had exercised an option on the $57.8 million contract “to ensure there will be no lapse in critical CVE services”, extending it for 11 months to 16 March 2026.[12] Just before the extension, a group of CVE Board members set up the CVE Foundation, a non-profit meant to safeguard the program’s independence.[19]

    This page has not confirmed the contract arrangements that followed the March 2026 option end date; the CVE Program continued publishing records through the third quarter of 2026.[5] For CISA’s wider role, see cisa.

    More in Cybersecurity

    Developing in AI & Computing

    Go deeper

    Questions readers ask

    What does a CVE ID look like?

    CVE, then a year, then a sequence number of four or more digits, such as CVE-2019-12345. The year is when the ID was reserved or the flaw made public, not when it was discovered.[7]

    Who assigns CVE IDs?

    CVE Numbering Authorities (CNAs), which include software vendors, researchers, open-source projects, CERTs and bug bounty providers, each within its own scope. Joining costs nothing and needs no contract.[3]

    Does a CVE record say how severe a flaw is?

    Not by itself. The CVE Program calls it a myth that it assigns severity scores. Severity is commonly expressed with FIRST's Common Vulnerability Scoring System (CVSS), now at version 4.0.[11][13]

    What is the difference between CVE and the NVD?

    CVE assigns IDs and publishes basic records. NIST's National Vulnerability Database has aimed to add details such as severity scores and product lists, but since April 2026 it enriches only prioritized CVEs, such as those on CISA's Known Exploited Vulnerabilities list.[1][6]

    Did the CVE program nearly shut down?

    In April 2025 MITRE warned that its government contract to run the program was expiring. CISA exercised an option to extend the $57.8 million contract for 11 months, to March 2026.[12]

    Sources

    · 19 claims from 6 publishers

    Each numbered claim is a statement we checked against the sources listed with it. Tap a number in the text to see its sources in place.

    1. [1]

      The CVE Program says its mission is to identify, define and catalog publicly disclosed cybersecurity vulnerabilities, with one CVE Record for each vulnerability. confirmedas of 2026-11-08

    2. [2]

      According to the CVE Program, IT and security professionals use CVE Records to make sure they are discussing the same issue and to coordinate prioritizing and fixing vulnerabilities. confirmedas of 2026-11-08

    3. [3]

      CVE Numbering Authorities are vendors, researchers, open-source projects, CERTs, hosted services, bug bounty providers and consortia authorized to assign CVE IDs and publish records within their own scopes, with no fee or contract to join. confirmedas of 2026-11-08

    4. [4]

      CVE Program metrics show 12,009, 11,701, 11,738 and 12,796 CVE Records published in the four quarters of 2025, a total of 48,244. confirmedas of 2026-11-08

    5. [5]

      CVE Program metrics show 36,962 CVE Records published in the third quarter of 2026, up from 15,154 in the first quarter and 20,696 in the second. confirmedas of 2026-11-08

    6. [6]

      On 15 April 2026 NIST said that its National Vulnerability Database, which had aimed to add details such as severity scores and product lists to all CVEs, would because of a 263% rise in CVE submissions between 2020 and 2025 enrich only prioritized CVEs, such as those in CISA's KEV catalog, those in software used by the federal government and critical software, and would label the rest lowest priority. confirmedas of 2026-11-08

      • NVD News · NIST · Primary source · April 15, 2026: NIST Updates NVD Operations to Address Record CVE Growth (retrieved 2026-11-08)
      • NVD News · NIST · Primary source · New Prioritization Criteria (retrieved 2026-11-08)
      • NVD News · NIST · Primary source · April 15, 2026: NIST Updates NVD Operations to Address Record CVE Growth (retrieved 2026-11-08)
      • NVD News · NIST · Primary source · New Prioritization Criteria (retrieved 2026-11-08)
      • NVD News · NIST · Primary source · New Prioritization Criteria (retrieved 2026-11-08)
    7. [7]

      A CVE ID takes the form CVE prefix, year and a sequence number of four or more digits; the year is when the ID was reserved or the vulnerability made public, not when it was discovered. confirmedas of 2026-11-08

    8. [8]

      Each CVE Record includes at minimum the CVE ID, a brief description of the vulnerability, affected products and versions, and pertinent references. confirmedas of 2026-11-08

    9. [9]

      In the CVE Record lifecycle, a vulnerability is discovered and reported to the CVE Program, the reporter requests a CVE ID that is then reserved, and the responsible CNA publishes the record once the minimum required data is included. confirmedas of 2026-11-08

    10. [10]

      The CVE Program says a Reserved ID lets stakeholders coordinate on a vulnerability early while the responsible CNA is not yet ready to disclose it publicly. confirmedas of 2026-11-08

    11. [11]

      The CVE Program lists as a myth that it is responsible for assigning vulnerability severity scores, and as another myth that it is run entirely by the MITRE Corporation. confirmedas of 2026-11-08

    12. [12]

      In April 2025, after a MITRE letter warned that funding for the CVE program was expiring, CISA said it had exercised an option on its $57.8 million contract with MITRE to keep the program running for 11 more months, to 16 March 2026. confirmedas of 2026-11-08

    13. [13]

      FIRST says the Common Vulnerability Scoring System captures a vulnerability's main characteristics as a numerical severity score that can be translated into ratings such as low, medium, high and critical, is used by organizations worldwide, and is currently at version 4.0. confirmedas of 2026-11-08

    14. [14]

      NIST said it enriched nearly 42,000 CVEs in 2025, 45% more than in any prior year, but that this was not enough to keep up with submissions. confirmedas of 2026-11-08

      • NVD News · NIST · Primary source · April 15, 2026 update (retrieved 2026-11-08)
    15. [15]

      To add a vulnerability to the KEV catalog, CISA requires reliable evidence of exploitation in the wild, an assigned CVE ID and clear remediation guidance. confirmedas of 2026-11-07

    16. [16]

      CISA's KEV catalog listed 1,769 vulnerabilities in catalog version 2026.11.06, released on 6 November 2026. confirmedas of 2026-11-06

    17. [17]

      Under BOD 22-01, agencies must remediate catalogued vulnerabilities within six months for CVE IDs assigned before 2021 and within two weeks for all others, unless CISA adjusts the timeline for grave risk. confirmedas of 2026-11-07

    18. [18]

      CISA says the KEV catalog can be a starting point for organizations' vulnerability management but should not be the only factor. confirmedas of 2026-11-07

    19. [19]

      Before the extension was announced, a group of CVE Board members set up the CVE Foundation, a non-profit intended to safeguard the program's independence. reportedas of 2026-11-08

    Revision history (1)
    1. Page created.

    Created Nov 8, 2026. Last reviewed by an editor on Nov 8, 2026. Next scheduled review: Feb 8, 2027.

    Cite this page

    "The CVE program: how software vulnerabilities get their IDs." ContentLora, updated Nov 8, 2026. https://contentlora.com/explain/cve-program-explained

    Spotted an error? Suggest a correction or emailcorrections@contentlora.com.