CVE Database
A CVE database is a structured, searchable catalogue of publicly disclosed software vulnerabilities, each identified by a unique CVE ID and recorded with a description, the affected products, references and a severity score. The canonical public source is the US National Vulnerability Database (NVD), which enriches the CVE List maintained by MITRE.
A CVE database catalogues known software vulnerabilities under one identifier, so everyone refers to the same flaw in the same way. Each entry carries a CVE ID in the form CVE-YYYY-NNNNN, a short description, the affected products and versions, and links to advisories and patches.
The CVE List is maintained by MITRE, which assigns the identifiers. The US National Vulnerability Database (NVD) then enriches each record with a CVSS severity score, a CWE weakness type and structured product data (CPE). Most security tools draw on both: MITRE for the identifier, NVD for the analysis.
A CVE record tells you what a flaw is and how severe it could be, but not whether it is being exploited. With roughly 40,000 new CVEs disclosed each year, a raw catalogue quickly becomes unmanageable, and severity alone does not tell a team what to fix first.
A CVE database is not a vulnerability scanner. A scanner detects which CVEs are present on your estate; the database is the reference catalogue those findings map back to.
Turning a catalogue into a decision takes exploitation signal. EPSS exploitation probability, CISA KEV confirmed-exploitation status and live honeypot telemetry separate the handful of CVEs that matter now from the tens of thousands that do not.
Precursor Intelligence unifies the CVE database with EPSS, CISA KEV, CWE impact weighting, threat-actor attribution and Shadowserver honeypot data behind one exploitation risk score. It is queryable through a REST API, a dashboard and a read-only MCP server, so an engineer or an AI agent can look up a CVE, its exploitation likelihood and its real-world status in a single call.