# CVE Exploit Priority Monitor – EPSS & Optional CVSS (`maydit/cve-exploit-priority-monitor`) Actor

Track daily FIRST EPSS probabilities, percentiles and score dates for a CVE watchlist. Save confirmed changes for patch-ticket workflows; optionally enrich with attributed NVD CVSS and descriptions. No API keys or asset scanning.

- **URL**: https://apify.com/maydit/cve-exploit-priority-monitor.md
- **Developed by:** [Brandt May](https://apify.com/maydit) (community)
- **Categories:** AI
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.80 / 1,000 saved observations

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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 Exploit Priority Monitor — illustrative workflow](https://mayd-it.com/assets/actor-banners/cve-exploit-priority-monitor-cabf0f16c216.png)

## CVE Exploit Priority Monitor – EPSS & Optional CVSS

Turn known CVE identifiers into dated exploit-probability observations for patch tickets and security dashboards. Track FIRST EPSS probability, percentile and score changes. Add NVD descriptions and attributed CVSS scores when you need extra severity context.

Built for MSPs, vulnerability-management teams and ticket automations that already have a CVE inventory. This Actor does not scan assets or determine whether a particular system is vulnerable.

### Start with a useful result

Paste one to ten CVE IDs. The default makes one small-batch request to FIRST, requires no key or proxy, and saves only actual scored observations. Open the dataset for records, `SUMMARY` for coverage, and `RUN_REPORT` for a readable run explanation.

#### Prioritize two existing patch tickets

Fetch current FIRST probability, percentile and date for Log4Shell and MOVEit without adding a second source dependency.

```json
{
  "cveIds": ["CVE-2021-44228", "CVE-2023-34362"],
  "maxResults": 5,
  "includeNvdDetails": false
}
```

#### Check one CVE’s daily EPSS

Return the scored Log4Shell observation with explicit FIRST source and scoring date; NVD metadata is not requested.

```json
{
  "cveIds": ["CVE-2021-44228"],
  "maxResults": 1,
  "includeNvdDetails": false
}
```

#### Filter a high-probability watchlist

Keep scored CVEs whose EPSS probability is at least 0.5. This is prioritization evidence, not an exposure verdict.

```json
{
  "cveIds": ["CVE-2021-44228", "CVE-2023-34362"],
  "minimumEpss": 0.5,
  "includeUnscored": false,
  "maxResults": 5,
  "includeNvdDetails": false
}
```

### Read the scores correctly

| Field | Meaning |
| --- | --- |
| `epssProbability` | A 0–1 probability of exploitation in the wild over the next 30 days from the scoring date. It is not a percentage or an asset-specific exposure verdict. |
| `epssPercentile` | The source percentile, also 0–1. It is separate from the probability. |
| `epssDate` | FIRST’s scoring date; distinct from this Actor’s `observedAt`. |
| `epssProbabilityChange` | Difference from the previous complete observation in the same snapshot. |
| `nvdStatus` | `not_requested` for the default mode; `available` only after a validated NVD response. |
| `sourceUrl` | The exact official source lookup for this observation. |

Every row includes `recordId`, `observedAt`, `contentHash`, `comparisonStatus` and `changedFields`. FIRST-only rows leave NVD description, CVSS, rejection status and NVD dates null. They do not claim that the CVE is analyzed, non-rejected or applicable to your systems. An identifier missing from a complete FIRST response is recorded in `SUMMARY.unscored` and produces no placeholder or billed result.

### Optional NVD enrichment

Set `includeNvdDetails:true` to fetch NVD details for each requested CVE after FIRST succeeds. This slower mode adds the official description, CVE status, publication/modification dates, CWE identifiers, references and all supported CVSS 2.0/3.0/3.1/4.0 scoring sources. Each CVSS score retains its version, source and Primary/Secondary attribution. The preferred score uses the highest version with a Primary score; a unique NVD Primary wins if several exist. Unresolved ambiguity remains null rather than selecting the highest numeric score.

NVD requests are paced at least 6.5 seconds apart, including before the first request. Public NVD availability varies. A requested enrichment failure produces a partial or failed run and preserves history; it never silently becomes an EPSS-only success. Confirmed observations from other CVEs may still appear in a partial dataset.

`includeUnscored` and `includeRejected` apply to NVD-enriched records. A confirmed NVD CVE without a FIRST score can retain null EPSS fields when `includeUnscored:true`. Rejected NVD records are filtered unless explicitly included. A valid NVD “not found” answer creates no result row.

### Compare complete checks

Set `comparePrevious:true` to establish a baseline and compare later runs. `onlyChanges:true` also enables comparison and skips unchanged observations; a correct repeat can save zero rows. History is separated by watchlist, filters, enrichment mode, `snapshotName` and result cap. Use a snapshot sequentially; conflicting concurrent writers cannot overwrite its history.

Only complete successful source collection and confirmed dataset writes advance history. Source failures, spending caps, output truncation, exhausted deadlines and unreached inputs preserve the previous baseline. Missing rows never establish removals. Scoring dates and source metadata dates are part of comparison, so a new date can count as a change without a different numeric score.

### Scope and limits

- One to ten exact CVE IDs; `maxResults` 1–100; `maxRunSeconds` 30–120.
- No asset discovery, scanning, exploit instructions or proof of compromise. EPSS is one prioritization signal, not complete organizational risk.
- FIRST is used for small lookups, not bulk mirroring. Model updates can affect scores; preserve scoring dates and source attribution.
- Exact output cap equal to the full selected set can be complete; actual truncation cannot.
- Documented public API routes only. No arbitrary URLs, credentials, proxies or authentication bypasses.
- HTTP 401/403/429 stops further source requests. At most one paced retry is allowed for a transient 502/503/504 or transport timeout/reset when the deadline permits it.

### Pricing

$0.003 per confirmed saved observation, plus the $0.00005 Actor-start event. Failed requests, invalid input, filtered rows and unchanged items skipped by `onlyChanges` are not billed as result rows. Apify’s displayed pricing and run spending cap govern the run.

EPSS data are provided by FIRST and Empirical Security; optional NVD data are provided by NIST. Public source access is free. Payment covers this Actor’s validation, normalization, comparisons and integrations.

### Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

#### [CISA KEV Watchlist Monitor - Catalog Changes and EPSS](https://apify.com/maydit/cisa-kev-watchlist-monitor)

Check whether CVEs in your EPSS watchlist also appear in CISA’s Known Exploited Vulnerabilities catalog.

1. Take the exact CVE identifiers from cveId and place a small selection in the companion input’s cveIds array.
2. Keep EPSS probability and scoring date separate from CISA inclusion, added date and required-action information.

EPSS estimates probability; KEV records known exploitation under CISA’s criteria. Absence from KEV is not proof of safety, and neither source establishes whether your asset is affected.

#### [OSV Package Advisory Monitor](https://apify.com/maydit/osv-package-advisory-monitor)

Connect a CVE review with advisories for the exact package versions in your own software inventory.

1. Supply verified ecosystem, package name and version values to the OSV Actor’s packages input. A CVE ID alone is not a package identifier.
2. Review advisory aliases and affected-version evidence before associating a package finding with a CVE watchlist row.

This is a manual identity review, not an automatic CVE-to-package or asset-exposure mapping. Preserve each advisory’s source and affected-version semantics.

### Integrations and support

Use the same small input with Apify tasks, schedules, webhooks, API, MCP or CSV/JSON exports. Include source timing, `nvdStatus` and `SUMMARY` when passing results to an AI assistant. This Actor is independently maintained by Mayd It and is not endorsed by the source providers.

Source documentation: [FIRST EPSS API](https://api.first.org/epss/) and [NVD developer guidance](https://nvd.nist.gov/developers/start-here).

For an issue, include the run link, a small reproducible input and the relevant `SUMMARY` failure. Never include secrets.

# Actor input Schema

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

One to ten exact CVE IDs from your vulnerability inventory. No targets or assets are scanned.

## `minimumEpss` (type: `number`):

0–1 probability threshold, not percent. An EPSS score does not establish exposure or severity.

## `includeUnscored` (type: `boolean`):

Applies only with NVD enrichment: preserve a confirmed NVD CVE when FIRST has no score, using null values. In FIRST-only mode, absent scores never produce placeholder rows.

## `includeRejected` (type: `boolean`):

Applies only with NVD enrichment. By default NVD-rejected records are filtered. FIRST-only mode does not check CVE rejection status and leaves isRejected null.

## `maxResults` (type: `integer`):

A billed result is one confirmed saved observation. Truncation prevents history advancement.

## `comparePrevious` (type: `boolean`):

The first complete run establishes history. Partial/failed/capped runs never advance it.

## `onlyChanges` (type: `boolean`):

Enables comparison. Unchanged runs may save zero rows. Source-date changes can count as changes.

## `snapshotName` (type: `string`):

1–80 letters, digits, underscores or hyphens. Inputs/filters/output cap also separate history.

## `maxRunSeconds` (type: `integer`):

One FIRST batch request by default. Optional NVD requests are paced 6.5 seconds each; shared upstream delays can make large enriched watchlists partial.

## `includeNvdDetails` (type: `boolean`):

Optional slower enrichment through the public NVD API, paced 6.5 seconds per request. NVD outages produce an explicit partial/failed run, never a silent EPSS-only fallback. The default checks FIRST only.

## Actor input object example

```json
{
  "cveIds": [
    "CVE-2021-44228",
    "CVE-2023-34362"
  ],
  "minimumEpss": 0,
  "includeUnscored": true,
  "includeRejected": false,
  "maxResults": 5,
  "comparePrevious": false,
  "onlyChanges": false,
  "snapshotName": "default",
  "maxRunSeconds": 120,
  "includeNvdDetails": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `report` (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-34362"
    ],
    "includeNvdDetails": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("maydit/cve-exploit-priority-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 = {
    "cveIds": [
        "CVE-2021-44228",
        "CVE-2023-34362",
    ],
    "includeNvdDetails": False,
}

# Run the Actor and wait for it to finish
run = client.actor("maydit/cve-exploit-priority-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 '{
  "cveIds": [
    "CVE-2021-44228",
    "CVE-2023-34362"
  ],
  "includeNvdDetails": false
}' |
apify call maydit/cve-exploit-priority-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,maydit/cve-exploit-priority-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/dpFnSzv8xbPhu181z/builds/xNFJj9PFnJVc9xp5c/openapi.json
