# Known Exploited Vulnerabilities Monitor — CVE Patch Alerts (`plaindata/known-exploited-vulnerabilities`) Actor

Actively exploited CVEs as a table: vendor, product, date added, remediation due date, ransomware use, CWE. Filter by vendor, keyword, date or CVE list. Data: CISA KEV catalog (CC0), not affiliated.

- **URL**: https://apify.com/plaindata/known-exploited-vulnerabilities.md
- **Developed by:** [plaindata](https://apify.com/plaindata) (community)
- **Categories:** Developer tools, News, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 result returneds

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

## Known Exploited Vulnerabilities Monitor — CVE Patch Alerts

Get the **CISA Known Exploited Vulnerabilities (KEV)** catalog as a clean table: every CVE that U.S. CISA confirms is being exploited in the wild, with remediation due date and ransomware use. Filter by vendor, keyword, date added or check a list of CVEs. Schedule it daily for patch-priority alerts.

### Input examples

```json
{ "lastDays": 30 }
{ "vendors": ["Microsoft", "Ivanti"], "addedSince": "2026-01-01", "ransomwareOnly": true }
{ "cveIds": ["CVE-2021-44228", "CVE-2023-4966"] }
```

### Output (one row per CVE)

| Field | Meaning |
|---|---|
| cveId | CVE identifier |
| vendorProject, product | Affected vendor and product |
| vulnerabilityName, shortDescription | CISA's name and description |
| dateAdded, dueDate | Date added to KEV; federal remediation due date |
| knownRansomwareCampaignUse | Known / Unknown |
| requiredAction, notes, cwes | Required action, reference links, CWE IDs |
| nvdUrl | NVD detail page |
| catalogVersion, catalogReleased, source | Catalog metadata |

### Data source & licence

Official KEV data from CISA's `cisagov/kev-data` repository, one download per run. CISA: "The KEV database is distributed under the Creative Commons 0 1.0 License. You may use this data in any legal manner." The catalog contains no personal data.

### Notes

Not affiliated with or endorsed by CISA or DHS. CISA logo/seal are not used.

# Actor input Schema

## `lastDays` (type: `integer`):

Used when 'Added since' and CVE list are empty.

## `addedSince` (type: `string`):

YYYY-MM-DD; overrides 'last N days'.

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

Match vendor or product name, e.g. Microsoft, Cisco, Ivanti.

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

Match vulnerability name or description, e.g. remote code execution.

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

Check whether specific CVEs are in KEV, e.g. CVE-2021-44228. Date filter is ignored.

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

Only entries CISA marks as used in ransomware campaigns.

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

Newest first.

## Actor input object example

```json
{
  "lastDays": 30,
  "ransomwareOnly": false,
  "maxItems": 500
}
```

# 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 = {
    "lastDays": 30
};

// Run the Actor and wait for it to finish
const run = await client.actor("plaindata/known-exploited-vulnerabilities").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 = { "lastDays": 30 }

# Run the Actor and wait for it to finish
run = client.actor("plaindata/known-exploited-vulnerabilities").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 '{
  "lastDays": 30
}' |
apify call plaindata/known-exploited-vulnerabilities --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,plaindata/known-exploited-vulnerabilities"
        }
    }
}
```

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/YizaQjAbZAsSKXLjE/builds/Le8BgOVjFPujczoGy/openapi.json