# CVE Vulnerability Feed: NVD, CISA KEV & EPSS (`tacps126/cve-feed`) Actor

New and updated vulnerabilities from NVD with CVSS score and severity, CWE, affected vendors and products, references, CISA known-exploited status (date added, due date, ransomware use) and EPSS exploit likelihood. Filters by vendor, product, severity, CVSS, EPSS; alerts.

- **URL**: https://apify.com/tacps126/cve-feed.md
- **Developed by:** [Tapaswai Choudhary](https://apify.com/tacps126) (community)
- **Categories:** Developer tools, Automation
- **Security:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.40 / 1,000 vulnerabilities

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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

## CVE Vulnerability Feed — NVD, CISA KEV & EPSS

New and updated vulnerabilities from **NVD** in one clean feed, each with **CVSS score and severity**, weakness types (CWE), affected **vendors and products**, references, whether it is **known exploited** (CISA KEV: date added, remediation due date, ransomware use) and its **EPSS** probability of exploitation. Filter to your stack and get only new CVEs every day. Or watch CISA's known-exploited catalog for new additions.

**Built for** security and IT teams, MSPs and MSSPs, vulnerability-management and GRC vendors, threat-intelligence analysts, and AI agents.

### What you get

| Field | Meaning |
|---|---|
| `cveId`, `url`, `published`, `lastModified`, `status`, `description` | The CVE |
| `cvssScore`, `severity`, `cvss` (vector, version, attack vector) | How bad it is |
| `cwe` | Weakness types |
| `vendors`, `products`, `cpes` | What is affected |
| `knownExploited`, `kev` (date added, due date, required action, ransomware use) | Exploited in the wild (CISA) |
| `epss`, `epssPercentile` | Chance of exploitation in the next 30 days (FIRST) |
| `publicExploitReference`, `references` | Advisories, patches, exploit links |

### Why this Actor

- **Three sources joined:** NVD, CISA KEV and EPSS in one row.
- **Filters:** vendors, products, keywords, severity, minimum CVSS, known exploited only, minimum EPSS.
- **Alerts:** *Only new CVEs* + a daily schedule, to Slack, email, Jira (via webhooks) or Google Sheets.
- **Two modes:** everything new in NVD, or CVEs newly added to CISA's known-exploited list.
- **For AI agents.** Callable as an MCP tool.

### How to use it

Critical and high CVEs for your vendors, as a daily alert:

```json
{ "withinDays": 2, "vendors": ["microsoft", "cisco", "fortinet"], "severities": ["CRITICAL", "HIGH"], "onlyNew": true }
```

Newly known-exploited vulnerabilities this week:

```json
{ "source": "kev", "withinDays": 7 }
```

### Pricing

**$3 per 1,000 vulnerabilities** plus a small start fee per run. On the Apify free plan a run returns up to 100 vulnerabilities.

### Good to know

- New CVEs often have no CVSS or EPSS score for a few days until NVD and FIRST analyse them.
- For long date ranges, add your free NVD API key (optional) to read about 10× faster.
- Questions: **tacps126@gmail.com**.

# Actor input Schema

## `source` (type: `string`):

NVD: every CVE published or modified in the window. KEV: CVEs CISA added to its known-exploited catalog in the window.

## `withinDays` (type: `integer`):

About 600-900 CVEs are published a day.

## `dateFrom` (type: `string`):

YYYY-MM-DD; with To date replaces the days above.

## `dateTo` (type: `string`):

YYYY-MM-DD (default today).

## `dateType` (type: `string`):

NVD only.

## `keywords` (type: `string`):

Words in the CVE description, e.g. "remote code execution".

## `vendors` (type: `array`):

e.g. microsoft, apache, cisco (matches affected vendors).

## `products` (type: `array`):

e.g. windows, exchange server, log4j.

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

Empty = all.

## `minCvss` (type: `number`):

e.g. 7.

## `knownExploitedOnly` (type: `boolean`):

Only CVEs in CISA's known-exploited catalog.

## `minEpss` (type: `number`):

Probability of exploitation in the next 30 days, 0 to 1, e.g. 0.1.

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

Look up these CVEs instead (e.g. CVE-2024-3400).

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

Most CVEs returned per run.

## `onlyNew` (type: `boolean`):

Schedule the Actor and each run returns only CVEs earlier runs did not deliver: alerts for your vendors and products.

## `monitorName` (type: `string`):

Optional name for the “only new” history, so several monitors can run side by side.

## `tenantId` (type: `string`):

Optional label used to keep separate histories for different clients or teams.

## `nvdApiKey` (type: `string`):

Your free key from nvd.nist.gov makes long date ranges about 10× faster. Not needed for daily runs.

## `debug` (type: `boolean`):

Save extra diagnostics with the run (for support requests).

## Actor input object example

```json
{
  "source": "nvd",
  "withinDays": 2,
  "dateType": "published",
  "vendors": [],
  "knownExploitedOnly": false,
  "maxItems": 1000,
  "onlyNew": false,
  "debug": false
}
```

# Actor output Schema

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

The produced items (default dataset items).

# 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 = {
    "withinDays": 2,
    "vendors": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("tacps126/cve-feed").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 = {
    "withinDays": 2,
    "vendors": [],
}

# Run the Actor and wait for it to finish
run = client.actor("tacps126/cve-feed").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 '{
  "withinDays": 2,
  "vendors": []
}' |
apify call tacps126/cve-feed --silent --output-dataset

```

## MCP server setup

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

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/5fdzUyPAsqflurePT/builds/VPBfZTP4PSRJE0ULu/openapi.json