# NVD CVE Change History Scraper (`ninhothedev/nvd-cve-history-scraper`) Actor

$0.5/1K 🔥 NVD CVE History Scraper! Track CVE vulnerability records, change history, CVSS scores & references from the NVD. No key. JSON, CSV, Excel or API in seconds. Feed a security-monitoring or threat-intel tool ⚡

- **URL**: https://apify.com/ninhothedev/nvd-cve-history-scraper.md
- **Developed by:** [ninhothedev](https://apify.com/ninhothedev) (community)
- **Categories:** Developer tools, Automation, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## NVD CVE Change History Scraper

**The audit trail of the National Vulnerability Database.** This actor scrapes the [NVD CVE change history API](https://services.nvd.nist.gov/rest/json/cvehistory/2.0) and returns **one row per change event** — *who* changed *what* on a CVE and *when*: re-analysis, rejection, CVSS re-scoring, CWE remaps, reference edits, SSVC additions and more.

No API key required. ~$0.5 per 1,000 change events.

### What makes this different from my other CVE actors

This is **not** another "current state of a CVE" scraper. It is the **change/audit history** — the log of modifications over a CVE's lifetime.

| Actor | What it gives you |
|-------|-------------------|
| [circl-cve-scraper](https://apify.com/ninhothedev/circl-cve-scraper) | The current CVE record (description, CVSS, references) from CIRCL |
| [nist-cpe-scraper](https://apify.com/ninhothedev/nist-cpe-scraper) | CPE product/platform dictionary entries |
| [cisa-kev-scraper](https://apify.com/ninhothedev/cisa-kev-scraper) | CISA Known Exploited Vulnerabilities catalog |
| [epss-scores-scraper](https://apify.com/ninhothedev/epss-scores-scraper) | EPSS exploit-probability scores |
| **nvd-cve-history-scraper (this one)** | **The change log: every modification event on a CVE (re-analysis, rejection, CVSS change) with old vs. new values** |

If you want the *current* state of a CVE, use one of the others. If you want to know *how a CVE record has changed over time* — for audit trails, compliance evidence, or catching silently re-scored vulnerabilities — this is the one.

### Modes

- **`window`** — every change event inside a date range (default = the last 7 days).
- **`cves`** — the full change history for one or more specific CVE ids (e.g. Log4Shell `CVE-2021-44228`).

### Use cases

- **Vulnerability-management audit trails** — a defensible log of when and how a CVE record changed.
- **CVE lifecycle tracking** — follow a CVE from *Received* → *Initial Analysis* → *Modified* → *Reanalysis*.
- **Detecting re-scored CVEs** — flag CVEs whose CVSS was quietly raised or lowered (`affects_cvss`).
- **Compliance** — evidence that your triage reflects the latest NVD analysis.

### Input

| Field | Type | Description |
|-------|------|-------------|
| `mode` | select | `window` (date range, default) or `cves` (history for specific ids). |
| `cves` | array | CVE ids to fetch when `mode = cves`, e.g. `["CVE-2021-44228"]`. |
| `changeStartDate` | string | Window start `YYYY-MM-DD` (UTC). Default = 7 days ago. |
| `changeEndDate` | string | Window end `YYYY-MM-DD` (UTC). Default = now. |
| `eventNameFilter` | string | Keep only events with this exact name, e.g. `CVE Rejected`. |
| `apiKey` | string | Optional NVD key — raises the rate limit. |
| `maxItems` | integer | Max change events for the run (default 200, max 5000). |

### Output

One dataset row per change event:

```json
{
  "type": "cve_change",
  "cve_id": "CVE-2021-44228",
  "change_id": "4485E73F-35C2-4A94-82B4-D644383FDC73",
  "event_name": "Reanalysis",
  "source_identifier": "nvd@nist.gov",
  "created": "2021-12-14T19:15:00.000000Z",
  "detail_count": 2,
  "changes": [
    {"action": "Changed", "type": "CVSS V3.1", "old_value": "...", "new_value": "..."}
  ],
  "changed_fields": ["CVSS V3.1", "CWE"],
  "is_rejection": false,
  "is_reanalysis": true,
  "affects_cvss": true,
  "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-44228",
  "source": "nvd-cvehistory",
  "scraped_at": "2026-08-11T00:00:00.000000Z"
}
```

Event names you will see include: `New CVE Received`, `Initial Analysis`, `CVE Modified`, `Modified Analysis`, `Reanalysis`, `CVE Rejected`, `CWE Remap`, `CPE Deprecation Remap`. Detail `type` values include `Description`, `CVSS V2`, `CVSS V3.1`, `CWE`, `Reference`, `Affected`, `CPE Configuration`, `SSVC`.

### Rate limits & the 120-day window cap

- **Keyless:** NVD allows roughly **5 requests per 30 seconds**. The actor spaces requests ~6s apart and backs off on HTTP 403/429. Supplying a free NVD `apiKey` raises the limit and speeds up large runs.
- **120-day window cap:** NVD rejects change windows longer than 120 days. The actor **automatically splits** longer ranges into 120-day chunks, so you can request any span.

### Notes

Values for each field-level change are capped at 300 characters and the per-event `changes` list is capped at 30 entries to keep rows lightweight; `detail_count` and `changed_fields` always reflect the full set.

# Actor input Schema

## `mode` (type: `string`):

How to query the NVD change history. 'window' returns every change event inside a date range (default = last 7 days). 'cves' returns the full change history for the CVE ids you list.

## `cves` (type: `array`):

Used when mode = 'cves'. List of CVE ids to fetch the change history for, e.g. \["CVE-2021-44228"]. Ignored in window mode.

## `changeStartDate` (type: `string`):

Window mode only. Start of the change window as YYYY-MM-DD (UTC). Defaults to 7 days ago if empty. NVD caps each window at 120 days; longer ranges are auto-split.

## `changeEndDate` (type: `string`):

Window mode only. End of the change window as YYYY-MM-DD (UTC). Defaults to now if empty.

## `eventNameFilter` (type: `string`):

Optional. Keep only change events whose event name matches exactly, e.g. 'CVE Rejected', 'Reanalysis', 'CVE Modified', 'Modified Analysis', 'Initial Analysis'. Leave empty for all.

## `apiKey` (type: `string`):

Optional NVD API key. Keyless access is limited to ~5 requests / 30s; a free key raises the limit and speeds up large runs. Get one at nvd.nist.gov/developers/request-an-api-key.

## `maxItems` (type: `integer`):

Maximum number of change events to return across the whole run.

## Actor input object example

```json
{
  "mode": "window",
  "cves": [
    "CVE-2021-44228",
    "CVE-2014-0160"
  ],
  "changeStartDate": "2026-08-01",
  "changeEndDate": "2026-08-05",
  "eventNameFilter": "CVE Rejected",
  "maxItems": 200
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "cves": [
        "CVE-2021-44228"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ninhothedev/nvd-cve-history-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "cves": ["CVE-2021-44228"] }

# Run the Actor and wait for it to finish
run = client.actor("ninhothedev/nvd-cve-history-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "cves": [
    "CVE-2021-44228"
  ]
}' |
apify call ninhothedev/nvd-cve-history-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ninhothedev/nvd-cve-history-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/TpQvOAX3l8OvjnR1Y/builds/Y7OpJtzQhgg2mcuGp/openapi.json