# CISA KEV monitor (Known Exploited Vulnerabilities + NVD) (`keepable_injera/cisa-kev-monitor`) Actor

Filter the CISA KEV catalog and enrich results with NVD CVSS and CWE data.

- **URL**: https://apify.com/keepable_injera/cisa-kev-monitor.md
- **Developed by:** [Chee Chiaw Lim](https://apify.com/keepable_injera) (community)
- **Categories:** Developer tools, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

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

## CISA KEV monitor (Known Exploited Vulnerabilities + NVD)

This Apify Actor returns vulnerabilities from the CISA Known Exploited Vulnerabilities Catalog. It filters the catalog by date, vendor, product, and reported ransomware use, then optionally adds NVD severity and weakness data.

### Coverage and source

The catalog identifies vulnerabilities that CISA reports as exploited in the wild. Use it to monitor additions and route remediation work. A CVE's `dateAdded` determines inclusion, rather than its publication date or last modification date.

The source is the [CISA KEV JSON feed](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json). Optional enrichment uses the [NVD CVE API](https://services.nvd.nist.gov/rest/json/cves/2.0). For full CVE feeds beyond KEV, use the [NVD CVE monitor Actor](https://apify.com/keepable_injera/nvd-cve-monitor).

### Input

| Field | Default | Meaning |
| --- | --- | --- |
| `sinceDays` | 30 | Include records whose `dateAdded` is on or after midnight UTC N days ago. Use 0 for the whole catalog. |
| `vendors` | \[] | Case-insensitive exact matches on `vendorProject`. Empty selects all vendors. |
| `products` | \[] | Case-insensitive substrings of `product`. Empty selects all products. |
| `ransomwareOnly` | false | Include only records whose `knownRansomwareCampaignUse` is `Known`. |
| `enrichWithNvd` | true | Add NVD CVSS, CWE, publication, modification, and status fields. |
| `nvdMaxLookups` | 25 | Maximum NVD lookups per run. Later records retain null NVD fields. |
| `onlyNew` | false | Skip CVE IDs previously emitted to the named state store. |
| `maxItems` | 100 | Integer from 1 to 10000. Maximum records emitted per run. |
| `stateStoreName` | `cisa-kev-monitor-state` | Named key-value store for seen CVE IDs across runs. |

Filters run locally after the Actor fetches the full catalog. Values within each list match any entry. All active filters must match. Results sort by `dateAdded` descending, then `cveId` ascending. The catalog is one JSON document and has no paging.

### Output

Each record contains KEV details, catalog version, optional NVD fields, source attribution, and run metadata. KEV `cwes` and NVD `nvdCweIds` remain separate.

Example record with NVD enrichment disabled follows.

```json
{
  "cveId": "CVE-2026-41709",
  "vendorProject": "Broadcom",
  "product": "VMware ESX",
  "vulnerabilityName": "Broadcom VMWare ESX Insufficient Logging Vulnerability",
  "dateAdded": "2026-10-28",
  "shortDescription": "Broadcom VMWare ESX contains an insufficient logging vulnerability that could allow a malicious actor with admin access to perform certain operations without being logged.",
  "requiredAction": "Apply mitigations in accordance with vendor instructions.",
  "dueDate": "2026-11-11",
  "knownRansomwareCampaignUse": "Unknown",
  "notes": "https://nvd.nist.gov/vuln/detail/CVE-2026-41709",
  "cwes": ["CWE-778"],
  "catalogVersion": "2026.10.29",
  "cvssVersion": null,
  "cvssBaseScore": null,
  "cvssSeverity": null,
  "cvssVector": null,
  "nvdCweIds": null,
  "nvdPublished": null,
  "nvdLastModified": null,
  "nvdStatus": null,
  "nvdError": null,
  "nvdUrl": "https://nvd.nist.gov/vuln/detail/CVE-2026-41709",
  "relatedActor": "https://apify.com/keepable_injera/nvd-cve-monitor",
  "source": "CISA Known Exploited Vulnerabilities Catalog",
  "sourceUrl": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
  "licence": "CC0 1.0 (https://www.cisa.gov/sites/default/files/licenses/kev/license.txt)",
  "disclaimer": "This product uses the NVD API but is not endorsed or certified by the NVD. Not endorsed by CISA or DHS.",
  "generatedId": "KEV:CVE-2026-41709",
  "changeType": "new",
  "scrapedAt": "2026-10-30T00:00:00.000Z"
}
```

The example shortens `requiredAction` and `notes`. Actual output retains source text. The dataset has a table view of key fields. `RUN_SUMMARY` in the default key-value store records timestamps, counts, charge-limit status, and any run error.

NVD metrics prefer a Primary CVSS v3.1 metric, then the first v3.1 metric. If v3.1 is absent, the Actor tries v3.0 and then v4.0. `cvssVersion` identifies the chosen version. Missing values remain null. An NVD request failure sets `nvdError` and leaves the KEV record available.

### State and pricing

The state store keeps seen CVE IDs under one key. An absent ID gets `changeType: "new"`; a stored ID gets `"seen"`. Only successful pushes enter the set. With `onlyNew` false, previously emitted CVEs appear again. This tracks first emission, not changes to an existing CVE. Use a separate state store for independent monitors.

If permission to open a named store is denied with HTTP 403, the Actor warns, uses the default store, and disables `onlyNew` for that run.

Pricing is $0.002 per result, no start fee. Each emitted record uses the `result` billing event. The Actor stops at the available charge limit. Records skipped by `onlyNew` do not incur a result charge. Platform compute and storage charges may apply separately.

### Licence and disclaimer

The KEV feed is licensed under [CC0 1.0](https://www.cisa.gov/sites/default/files/licenses/kev/license.txt). Every record carries the source, source URL, licence, and disclaimer.

This product uses the NVD API but is not endorsed or certified by the NVD. Not endorsed by CISA or DHS.

### Limits

The feed and NVD may lag vendor disclosures or contain omissions. Catalog membership and severity data do not replace an assessment of your systems. Due dates and required actions retain CISA's source wording.

NVD enrichment uses no API key. Public NVD access allows 5 requests per 30 seconds. The Actor waits at least 6.5 seconds between NVD calls and caps enrichment at `nvdMaxLookups`. HTTP 429, server errors, and timeouts do not fail the run. Failed lookups count toward the cap. Disable enrichment to avoid the NVD wait. A KEV feed failure stops the run and appears in `RUN_SUMMARY`.

### Local verification

Run the offline tests with `npm test`. For a fixture-backed local run, write an input file with `sinceDays` set to 0 and use fresh local storage.

```sh
mkdir -p /tmp/kev-verification/key_value_stores/default
printf '%s\n' '{"sinceDays":0,"enrichWithNvd":true,"nvdMaxLookups":2,"maxItems":3}' > /tmp/kev-verification/key_value_stores/default/INPUT.json
APIFY_LOCAL_STORAGE_DIR=/tmp/kev-verification CRAWLEE_STORAGE_DIR=/tmp/kev-verification APIFY_PURGE_ON_START=false NODE_OPTIONS='--import ./scripts/offline-fixture.js' npm start
node scripts/verify-output.js /tmp/kev-verification
```

The preload serves the KEV fixture and a hand-written NVD fixture. It blocks other network requests. The verifier reads saved dataset records and `RUN_SUMMARY`. This run checks local behavior, not current API availability.

# Actor input Schema

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

dateAdded >= midnight UTC N days ago. Zero selects the whole catalog.

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

Case-insensitive exact vendorProject names. Empty selects all.

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

Case-insensitive product substrings. Empty selects all.

## `ransomwareOnly` (type: `boolean`):

Select known ransomware campaign use.

## `enrichWithNvd` (type: `boolean`):

Look up NVD CVSS and CWE data for emitted results.

## `nvdMaxLookups` (type: `integer`):

Maximum NVD lookups per run. Remaining records have null NVD fields.

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

Skip CVE IDs already emitted to the state store.

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

Maximum results emitted after filtering and onlyNew.

## `stateStoreName` (type: `string`):

Named store for cross-run seen CVE IDs. A 403 falls back to the default store and disables onlyNew.

## Actor input object example

```json
{
  "sinceDays": 30,
  "vendors": [],
  "products": [],
  "ransomwareOnly": false,
  "enrichWithNvd": true,
  "nvdMaxLookups": 25,
  "onlyNew": false,
  "maxItems": 100,
  "stateStoreName": "cisa-kev-monitor-state"
}
```

# Actor output Schema

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

No description

## `runSummary` (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 = {
    "sinceDays": 30,
    "vendors": [],
    "products": [],
    "ransomwareOnly": false,
    "enrichWithNvd": true,
    "nvdMaxLookups": 25,
    "onlyNew": false,
    "maxItems": 100,
    "stateStoreName": "cisa-kev-monitor-state"
};

// Run the Actor and wait for it to finish
const run = await client.actor("keepable_injera/cisa-kev-monitor").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 = {
    "sinceDays": 30,
    "vendors": [],
    "products": [],
    "ransomwareOnly": False,
    "enrichWithNvd": True,
    "nvdMaxLookups": 25,
    "onlyNew": False,
    "maxItems": 100,
    "stateStoreName": "cisa-kev-monitor-state",
}

# Run the Actor and wait for it to finish
run = client.actor("keepable_injera/cisa-kev-monitor").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 '{
  "sinceDays": 30,
  "vendors": [],
  "products": [],
  "ransomwareOnly": false,
  "enrichWithNvd": true,
  "nvdMaxLookups": 25,
  "onlyNew": false,
  "maxItems": 100,
  "stateStoreName": "cisa-kev-monitor-state"
}' |
apify call keepable_injera/cisa-kev-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,keepable_injera/cisa-kev-monitor"
        }
    }
}
```

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/bxGggnt86dOtl8T2x/builds/aghzFRhP7VNys4tVD/openapi.json