# NVD CVE Scraper - Vulnerabilities, CVSS, CWE & CPE (`thirdwatch/nvd-cve-scraper`) Actor

Search the official NIST National Vulnerability Database CVE 2.0 API. Export CVE descriptions, CVSS metrics, CWE weaknesses, affected CPEs, references, and CISA KEV fields.

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

## Pricing

from $2.00 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## NVD CVE Scraper

> Search NIST NVD vulnerabilities and export CVE descriptions, CVSS scores, CWE IDs, affected products, references, and CISA KEV status.

### What you get

Build a structured vulnerability feed from the National Vulnerability Database by keyword or exact CVE ID. Results combine severity and scoring details with weaknesses, affected product identifiers, advisory references, and Known Exploited Vulnerability fields for prioritization and reporting.

### Output fields

| Field | Description |
|---|---|
| `cve_id` | CVE identifier |
| `source_identifier` | Organization that supplied the record |
| `published` | Initial publication timestamp |
| `last_modified` | Latest NVD modification timestamp |
| `vulnerability_status` | Current record status |
| `description` | English vulnerability description |
| `cvss_version` | Selected CVSS version |
| `cvss_vector` | CVSS vector string |
| `cvss_score` | Base score |
| `severity` | Low, Medium, High, or Critical rating |
| `exploitability_score` | CVSS exploitability score when available |
| `impact_score` | CVSS impact score when available |
| `cwe_ids` | Associated CWE weakness identifiers |
| `affected_cpes` | Affected CPE product identifiers, including nested matches |
| `references` | Advisory URLs, sources, and tags |
| `known_exploited` | Whether NVD includes CISA KEV fields |
| `cisa_exploit_added` | Date added to CISA KEV |
| `cisa_action_due` | Federal remediation due date |
| `cisa_required_action` | CISA required action |
| `cisa_vulnerability_name` | CISA vulnerability name |
| `nvd_url` | Official NVD record |
| `query` | Keyword or CVE ID used |
| `source` | Source name |

### Example output

```json
{
  "cve_id": "CVE-2021-44228",
  "published": "2021-12-10T10:15:09.143",
  "description": "Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints.",
  "cvss_version": "3.1",
  "cvss_score": 10.0,
  "severity": "CRITICAL",
  "cwe_ids": ["CWE-502", "CWE-917"],
  "known_exploited": true,
  "nvd_url": "https://nvd.nist.gov/vuln/detail/CVE-2021-44228",
  "query": "CVE-2021-44228"
}
```

### Input parameters

| Parameter | Required | Description |
|---|---|---|
| `keywordQueries` | No | Product, vendor, or vulnerability searches. Defaults to `Apache`. |
| `cveIds` | No | Exact identifiers such as `CVE-2021-44228`. |
| `severities` | No | Any combination of `LOW`, `MEDIUM`, `HIGH`, and `CRITICAL`. |
| `onlyKnownExploited` | No | Keep only records with CISA Known Exploited Vulnerability fields. Defaults to false. |
| `maxResultsPerSearch` | No | Maximum matching CVEs per keyword or ID. Defaults to 10. |

### Use cases

- Security operations teams: monitor newly published critical vulnerabilities by product.
- Vulnerability managers: enrich asset and ticket records with CVSS, CWE, CPE, and KEV data.
- Researchers: build source-linked datasets for vulnerability trend analysis.
- Developers: schedule an export into a SIEM, risk dashboard, or remediation workflow.

### Limitations

NVD records evolve, and scoring or affected-product details may lag vendor advisories. Some CVEs lack CVSS, CWE, CPE, or CISA fields. Keyword matching searches descriptions rather than your private asset inventory. Validate remediation decisions against vendor advisories and the linked NVD record.

### Compared to alternatives

Compared with `benthepythondev/nvd-cve-scraper`, this Actor adds exact CVE lookup, severity filters, affected CPEs, and CISA KEV fields while starting at a lower base result price at publication. Compared with `compute-edge/nist-nvd-scraper`, it adds an explicit Known Exploited-only workflow and includes CISA action dates and required actions. Store pricing and features can change.

### FAQ

#### Can I look up one CVE without a keyword search?

Yes. Put the identifier in `cveIds` and clear `keywordQueries`.

#### Which CVSS version is returned?

The row uses the best available primary metric, preferring CVSS 4.0, then 3.1, 3.0, and 2.0.

#### Does known exploited mean the vulnerability is exploited everywhere?

No. It means the NVD record carries CISA KEV metadata. Use your exposure and asset context to prioritize action.

Explore more data products at [thirdwatch.dev](https://thirdwatch.dev). Related Thirdwatch Actors: [Google News Scraper](https://apify.com/thirdwatch/google-news-scraper), [Google Search Scraper](https://apify.com/thirdwatch/google-search-scraper), and [SEC EDGAR Scraper](https://apify.com/thirdwatch/sec-edgar-scraper).

Last verified: 2026-07

# Actor input Schema

## `keywordQueries` (type: `array`):

Search CVE descriptions for products, vendors, or vulnerability terms.

## `cveIds` (type: `array`):

Optional exact CVE identifiers such as CVE-2021-44228.

## `severities` (type: `array`):

Optional client-side severity filter.

## `onlyKnownExploited` (type: `boolean`):

Return only CVEs carrying CISA Known Exploited Vulnerability fields in NVD.

## `maxResultsPerSearch` (type: `integer`):

Stop after this many matching CVEs for each keyword or exact ID search.

## Actor input object example

```json
{
  "keywordQueries": [
    "Apache"
  ],
  "cveIds": [],
  "severities": [],
  "onlyKnownExploited": false,
  "maxResultsPerSearch": 10
}
```

# 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 = {
    "keywordQueries": [
        "Apache"
    ],
    "onlyKnownExploited": false,
    "maxResultsPerSearch": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("thirdwatch/nvd-cve-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 = {
    "keywordQueries": ["Apache"],
    "onlyKnownExploited": False,
    "maxResultsPerSearch": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("thirdwatch/nvd-cve-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 '{
  "keywordQueries": [
    "Apache"
  ],
  "onlyKnownExploited": false,
  "maxResultsPerSearch": 10
}' |
apify call thirdwatch/nvd-cve-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thirdwatch/nvd-cve-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/nGu8r57fwfkbdeCLx/builds/O43DIMm9m3i0v8RCj/openapi.json