shipapis
StarSubmit an APISubmit API

National Vulnerability Database

The US government's CVE vulnerability database

🔐 SecurityDYINGchecked 12h ago
AUTH NONECORS ✗AGENT ✓HTTPS ✓COMMERCIAL ✓

NIST's National Vulnerability Database offers the canonical REST feed for CVE records, complete with descriptions, CVSS scores, and references. Look up a single CVE by ID or page through the whole corpus. Keyless access is capped at five requests per 30 seconds; a free key lifts that ceiling.

78HOW IT'S SCORED ⓘ
Docs ↗
Status badge · for your READMEshipapis health badge: 78 · dying
Uptime history
86.3%90 days
83.3%30 days
974P50 · ms
4777P95 · ms
operationalpartialdownno data
Response time · last 48 checks
Fastest 74 ms, slowest 2889 ms, most recent 511 ms.
Live response samplecaptured by our last successful check
GET https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2019-1010218

{
  "resultsPerPage": 1,
  "startIndex": 0,
  "totalResults": 1,
  "format": "NVD_CVE",
  "version": "2.0",
  "vulnerabilities": [
    {
      "cve": {
        "id": "CVE-2019-1010218",
        "sourceIdentifier": "josh@bress.net",
        "published": "2019-07-22T18:15:10.917",
        "vulnStatus": "Modified"
      }
    }
  ]
}
Call itcurl · fetch · python
curl "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2019-1010218"
const res = await fetch("https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2019-1010218");
const data = await res.json();
console.log(data);
import requests

res = requests.get("https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2019-1010218")
print(res.json())

BROWSER CALLS BLOCKED (NO CORS/HTTPS) — USE THE CURL SNIPPET

Endpoints · 6DyingFULL DOCS ↗
Dying — error rate climbing on GET /cves/2.0?cveId=CVE-2019-1010218974 mschecked 12h ago
GET/cves/2.0?cveId=CVE-2019-1010218PROBED

The US government's CVE vulnerability database

GET/cves

Cves — documented GET route.

GET/cves/1

Cves details by ID (example: 1).

GET/cves?limit=10

Cves — documented GET route.

GET/cves/search?q=test

Search by query parameters.

GET/cves/2.0?limit=5

2 0 — documented GET route.

Machine-readable spec

We probe a documented GET and expect 2xx JSON — full uptime and health score. Export includes every documented route below.

Response-shape history

Stable. No schema drift observed since monitoring began — the response shape has not changed under our checks.

National Vulnerability Database: common questions

Is National Vulnerability Database free to use?

Yes — National Vulnerability Database is a free security API. Free tier: Free — no key required (free key raises limits). Commercial use is allowed on the free tier.

Does National Vulnerability Database need an API key?

No — National Vulnerability Database needs no API key or signup. You can call it straight away; rate limits still apply (5 requests per rolling 30 seconds without an API key (50 with a free key)).

Can I call National Vulnerability Database from the browser?

Not directly — National Vulnerability Database doesn't send browser-friendly CORS headers, so call it from a server or proxy instead. Copy the curl or Python snippet on this page to get started.

Is National Vulnerability Database up right now?

As of our last scheduled check, National Vulnerability Database is dying with 86.3% uptime over 90 days and a 974 ms median response. We re-probe it every sweep — the status badge and uptime chart above always show the latest.