NVD (National Vulnerability Database) CVE API
National Institute of Standards and Technology (NIST)
Every publicly known software vulnerability, scored for severity and tied to affected products.
The U.S. government's enriched copy of the CVE list: each vulnerability gets a description, CVSS severity scores, weakness type (CWE), and machine-readable lists of affected product versions (CPE). Security teams use it to prioritize patching, and researchers use it to study how vulnerabilities are found and disclosed over time.
Access
- Cost
- FreeFree; an optional free API key raises rate limits.
- License
- Public domainU.S. government work; NVD data is in the public domain
- Sign-up
- No sign-up
- How you get it
- API and Bulk downloadJSON
What's in it
- One row is
- One record per CVE vulnerability
- Covers
- Global software
- Years
- 1999-present (some entries describe older flaws)
- Updated
- Real time
- Size
- Hundreds of thousands of CVE records
Quality
The reference source for CVE severity and affected products, but NIST's analysis fell badly behind in 2024, leaving many recent CVEs unenriched.
- Analysis backlog since 2024 leaves many recent CVEs without scores or product lists
- CVE counts rise with reporting effort, not just with insecurity
- CPE product names are inconsistent
Connects to
- CISA Known Exploited Vulnerabilities Catalog: Flags which CVEs have been exploited in the wild
- Shodan: Estimate how many exposed devices run a vulnerable product
- PyPI Download Statistics (BigQuery): Track how fast users move off vulnerable package versions
Questions it could answer
- Which vendors have the most critical-severity CVEs per year?
- How has the median time from CVE publication to NVD scoring changed?