# CVE Exploit Priority: CISA KEV + EPSS in one call (`implementable_antler/cve-exploit-priority`) Actor

Paste CVE IDs or raw scanner text; get CISA KEV status (date added, due date, ransomware use) plus today's EPSS exploit probability, ranked P1/P2/P3 for patching. Built for agents and triage.

- **URL**: https://apify.com/implementable_antler/cve-exploit-priority.md
- **Developed by:** [Blake Runckel](https://apify.com/implementable_antler) (community)
- **Categories:** Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 cve checkeds

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

## CVE Exploit Priority: CISA KEV + EPSS in one call

Paste CVE IDs, or any raw text such as scanner output, an advisory or a ticket. For each CVE you get:

- **CISA KEV status:** whether the CVE is in the Known Exploited Vulnerabilities catalog, the date it was added, the federal remediation due date, known ransomware campaign use, vendor, product and required action.
- **EPSS:** today's probability that the CVE is exploited in the next 30 days, plus its percentile.
- **A patch-priority tier:** `P1-known-exploited` (in KEV), `P2-likely-exploited` (EPSS ≥ your threshold), `P3-monitor`, or `unscored` (EPSS has no score for the ID).

Rows are sorted P1 first. This makes it a one-step triage tool for AI agents, SOC workflows and vulnerability-management scripts.

### Input

| Field | Description |
|---|---|
| `cveIds` | One CVE ID per line. |
| `text` | Optional free text. Every `CVE-YYYY-NNNN` in it is extracted and de-duplicated. |
| `epssThreshold` | Default 0.1. A common field convention. EPSS itself recommends no universal threshold. |

### Output (per CVE)

`cve, priority, inKev, kevDateAdded, kevDueDate, kevRansomwareUse, kevVendor, kevProduct, kevName, kevRequiredAction, epss, epssPercentile, epssDate, kevCatalogVersion, checkedAt, nvdUrl, attribution`

### Limits

- EPSS is a likelihood estimate, not a risk score. It knows nothing about your environment. FIRST advises that KEV takes precedence when a CVE is listed, and the tiers follow that advice.
- The tiers are a simple rule (KEV, then EPSS threshold). They are not advice for your environment.
- Both sources are read live on every run, and nothing is cached across runs. EPSS updates daily around 13:30 UTC.

### Pricing

Pay per event: **$0.002 per CVE checked** (one dataset row), plus Apify's standard tiny Actor-start event.

### Sources and terms

- CISA Known Exploited Vulnerabilities catalog JSON feed, published under CC0 1.0 (https://www.cisa.gov/sites/default/files/licenses/kev/license.txt). Use of the data does not imply endorsement by CISA or DHS.
- EPSS scores from FIRST (https://api.first.org/data/v1/epss), published freely with no registration. Attribution is requested: See EPSS at https://www.first.org/epss. The API is limited to 1000 requests/min, and this Actor batches 100 CVEs per request.
  Not affiliated with CISA, DHS or FIRST.

Built by Ledger.

# Actor input Schema

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

One CVE ID per line.

## `text` (type: `string`):

Scanner output, an advisory, a ticket: every CVE-YYYY-NNNN in it is extracted.

## `epssThreshold` (type: `string`):

CVEs not in KEV with EPSS at or above this become P2. 0.1 is a common starting point, not an EPSS recommendation.

## `maxCves` (type: `integer`):

Safety cap per run.

## Actor input object example

```json
{
  "cveIds": [
    "CVE-2021-44228",
    "CVE-2023-4863",
    "CVE-2019-0708",
    "CVE-2020-1234"
  ],
  "epssThreshold": "0.1",
  "maxCves": 1000
}
```

# 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 = {
    "cveIds": [
        "CVE-2021-44228",
        "CVE-2023-4863",
        "CVE-2019-0708",
        "CVE-2020-1234"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("implementable_antler/cve-exploit-priority").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 = { "cveIds": [
        "CVE-2021-44228",
        "CVE-2023-4863",
        "CVE-2019-0708",
        "CVE-2020-1234",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("implementable_antler/cve-exploit-priority").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 '{
  "cveIds": [
    "CVE-2021-44228",
    "CVE-2023-4863",
    "CVE-2019-0708",
    "CVE-2020-1234"
  ]
}' |
apify call implementable_antler/cve-exploit-priority --silent --output-dataset

```

## MCP server setup

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

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/wgnM4PYAWbdcoWCVe/builds/bLZMQcO8D2ri40Q7W/openapi.json