# NIST National Vulnerability Database CVE API

> NIST NVD: 300,000+ CVEs with CVSS scores, CWE weaknesses, affected products and references

- Vendor: `nistnationalvulnerabilitydatab` · version 1.0 · category Cyber Security · tags cve api, nvd api, vulnerability database api, cvss api, security vulnerabilities api, cwe api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/nistnationalvulnerabilitydatab
- This document: https://apiclay.com/docs/nistnationalvulnerabilitydatab.md
- OpenAPI 3.1: https://apiclay.com/api/nistnationalvulnerabilitydatab/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `nistnationalvulnerabilitydatab`
- Updated: 2026-11-18

## About

## NIST National Vulnerability Database CVE API

The CVE API of the US National Vulnerability Database run by NIST: search every published CVE by keyword, severity, publication or modification dates, affected product (CPE) or the CISA known-exploited list, and fetch one CVE by id, each with descriptions, status, CVSS v2, v3.1 and v4 metrics, CWE weaknesses, affected product configurations and references.

Data comes from **nvd.nist.gov** (https://nvd.nist.gov). Every route calls the source's own public API and returns it unchanged.

Typical flow: `POST /cves?keywordSearch=openssl&amp;cvssV3Severity=CRITICAL&amp;resultsPerPage=20`, then `POST /cve?cveId=CVE-2024-3094`.

### Routes

#### POST `/cves` - Search CVEs
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| keywordSearch | query | string | no | Words in the description, e.g. `openssl`. |
| cvssV3Severity | query | string | no | `LOW`, `MEDIUM`, `HIGH` or `CRITICAL`. |
| pubStartDate | query | string | no | ISO date-time, e.g. `2026-10-01T00:00:00.000`; send with `pubEndDate`, at most 120 days apart. |
| pubEndDate | query | string | no | ISO date-time end of the window. |
| cpeName | query | string | no | Affected product, e.g. `cpe:2.3:a:openssl:openssl:3.0.0:*:*:*:*:*:*:*`. |
| resultsPerPage | query | number | no | Up to 2000; keep it small, each CVE is a few KB. |
| startIndex | query | number | no | Results to skip. |

Returns: `totalResults`, `resultsPerPage`, `startIndex`, `timestamp` and `vulnerabilities`: each `cve` with `id`, `published`, `lastModified`, `vulnStatus`, `descriptions`, `metrics` (`cvssMetricV31`, `cvssMetricV40`, `cvssMetricV2`), `weaknesses`, `configurations`, `references`, CISA KEV fields when listed.

#### POST `/cve` - CVE by id
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| cveId | query | string | yes | CVE id, e.g. `CVE-2024-3094`. |

Returns: The same envelope with that one CVE.

### Caveats

- Without its own key, NVD allows about 5 requests per 30 seconds per caller; space out bulk pulls.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by nvd.nist.gov.

## Pricing

- Pay as you go: 0.01 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### POST /cves — Search CVEs
- Gateway: `POST https://api.apiclay.com/v1/api/nistnationalvulnerabilitydatab/cves`
- Public query params: `keywordSearch` (string), `cvssV3Severity` (string), `pubStartDate` (string), `pubEndDate` (string), `cpeName` (string), `resultsPerPage` (number), `startIndex` (number)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### POST /cve — CVE by id
- Gateway: `POST https://api.apiclay.com/v1/api/nistnationalvulnerabilitydatab/cve`
- Public query params: `cveId` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X POST "https://api.apiclay.com/v1/api/nistnationalvulnerabilitydatab/cves" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
