# NVD CVE Tracker by Vendor, Product, Severity (`v0iddo/nvd-cve-tracker`) Actor

Pull new/modified CVEs from NIST NVD. Filter by vendor/product (CPE), severity, CWE, keyword. One row per CVE — id, description, CVSS v3 score, vector, CWEs, affected CPEs, refs. AppSec cron watchlist. NIST NVD REST 2.0 (free, no auth).

- **URL**: https://apify.com/v0iddo/nvd-cve-tracker.md
- **Developed by:** [vøiddo](https://apify.com/v0iddo) (community)
- **Categories:** Business, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 cve extracteds

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 Tracker — by Vendor, Product, Severity

Pull newly-published or newly-modified CVEs from **NIST NVD**. Filter by vendor/product (CPE 2.3), severity, CWE, or keyword. One clean row per CVE — id, description, CVSS v3 score & vector, CWEs, affected CPEs, references, NVD URL.

Built **for cron**: pass `sinceDays: 1` for a daily AppSec watchlist of your tech stack.

### Inputs

```json
{
  "keywords": ["openssl", "cisco asa"],
  "cpeFilters": ["cpe:2.3:a:apache:*:*:*:*:*:*:*:*:*"],
  "severityFilters": ["HIGH", "CRITICAL"],
  "sinceDays": 7,
  "maxResultsPerQuery": 200
}
```

| input | default | notes |
|---|---|---|
| `keywords` | — | Free-text searches over CVE descriptions. Each is a separate query. |
| `cpeFilters` | — | CPE 2.3 match strings (wildcards allowed). Each is a separate query. |
| `severityFilters` | all | Limit to `LOW`, `MEDIUM`, `HIGH`, `CRITICAL` (CVSS v3). |
| `cweId` | — | Optional CWE filter (e.g. `CWE-89`). |
| `sinceDays` | `7` | `lastModified >= now - sinceDays`. NVD max window is 120 days. |
| `maxResultsPerQuery` | `200` | Cap per keyword/CPE query. NVD page size up to 2000. |
| `apiKey` | — | Optional NVD API key — boosts rate from 5/30s to 50/30s. |

### Output

One row per CVE (deduplicated across keyword/CPE queries):

| field | example |
|---|---|
| cveId | `CVE-2026-12345` |
| published | `2026-05-30T14:00:00.000` |
| lastModified | `2026-06-01T09:12:33.140` |
| vulnStatus | `Analyzed`, `Modified`, `Awaiting Analysis` |
| description | `In Apache HTTP Server <2.4.62, ...` |
| cvssV3Version | `3.1` |
| cvssV3BaseScore | `9.1` |
| cvssV3Severity | `CRITICAL` |
| cvssV3VectorString | `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` |
| exploitabilityScore | `3.9` |
| impactScore | `5.9` |
| cwes | `["CWE-119", "CWE-787"]` |
| affectedCpes | `["cpe:2.3:a:apache:http_server:2.4.61:*:*:*:*:*:*:*"]` |
| references | `["https://www.openssl.org/news/secadv/20260530.txt", ...]` |
| nvdUrl | `https://nvd.nist.gov/vuln/detail/CVE-2026-12345` |
| queryOrigin | `kw=openssl sev=CRITICAL` |

### Daily cron pattern

```json
{
  "cpeFilters": [
    "cpe:2.3:a:apache:*:*:*:*:*:*:*:*:*",
    "cpe:2.3:a:nginx:*:*:*:*:*:*:*:*:*",
    "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*"
  ],
  "severityFilters": ["HIGH", "CRITICAL"],
  "sinceDays": 1
}
```

### Real-world questions this answers

- **AppSec triage.** Daily firehose of HIGH+CRITICAL CVEs affecting our stack.
- **Vendor watch.** Anything new from Cisco / Microsoft / Red Hat?
- **Supply-chain audit.** New CVEs in a CPE-matched component.
- **Vulnerability research.** Filter by CWE for class-specific datasets.

### What it doesn't do

- No EPSS / KEV enrichment yet (those are separate FIRST.org / CISA feeds; planned).
- No vendor advisory PDFs — just NVD-stored references.
- No exploit-availability flag (NVD doesn't expose `exploit-db` mapping reliably).

### Maintained by

[vøiddo studio](https://voiddo.com) — small independent shop.

# Actor input Schema

## `keywords` (type: `array`):

Free-text searches over CVE descriptions. Each keyword is a separate query — results union'd. Example: \["openssl", "cisco asa"]. Leave empty if filtering by CPE only.

## `cpeFilters` (type: `array`):

Match CVEs against CPE 2.3 strings (with wildcards). Example: \["cpe:2.3:a:apache:*:*:*:*:*:*:*:*:*", "cpe:2.3:o:cisco:ios:*:*:*:*:*:*:*:\*"]. Each is a separate query.

## `severityFilters` (type: `array`):

Limit to CVEs with CVSS v3 severity in this set. Empty = all.

## `cweId` (type: `string`):

Optional CWE filter, e.g. "CWE-89" for SQL injection. Single value.

## `sinceDays` (type: `integer`):

Pull CVEs whose lastModified date is in the last N days (NVD treats new publications + score revisions equivalently). Max NVD window per request is 120 days.

## `maxResultsPerQuery` (type: `integer`):

Hard cap per query. NVD page size is 2000.

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

Optional NVD API key from nvd.nist.gov/developers/request-an-api-key. Without it, NVD throttles at 5 req/30s; with it, 50 req/30s. Leave blank if you don't have one.

## Actor input object example

```json
{
  "keywords": [],
  "cpeFilters": [],
  "severityFilters": [],
  "cweId": "",
  "sinceDays": 7,
  "maxResultsPerQuery": 200
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("v0iddo/nvd-cve-tracker").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 = {}

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

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

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

```

## CLI example

```bash
echo '{}' |
apify call v0iddo/nvd-cve-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=v0iddo/nvd-cve-tracker",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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