# CVE Monitor — KEV, EPSS, Risk & PoC (`adorable_woodworker/cerberus-cve-intel`) Actor

Search and enrich CVEs from global and regional feeds in one dataset. Filter by keyword, severity, CVSS, EPSS, CISA KEV, and public PoC signals. Get a composite risk score for faster triage — built for SOC, AppSec, and researchers.

- **URL**: https://apify.com/adorable\_woodworker/cerberus-cve-intel.md
- **Developed by:** [Saad Ouled Lafqui](https://apify.com/adorable_woodworker) (community)
- **Categories:** AI, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## CVE Monitor — KEV, EPSS, Risk & PoC

Search and enrich CVEs across global and regional feeds in one dataset. Filter by keyword, severity, CVSS, EPSS, CISA KEV, and public PoC signals. Get a composite risk score for faster triage — built for SOC, AppSec, and researchers.

**No API key required.** Run the Actor, set filters, download results.

### What you get

Each dataset row is one enriched CVE, including:

- CVE ID, title, severity, CVSS
- EPSS exploit probability
- CISA KEV flag (`is_kev`)
- Public PoC / exploit signal (`has_poc`)
- Composite **risk score** (0–100)
- Published / modified timestamps and source signals

Feeds covered include **NVD**, **CNVD**, **EUVD**, **CISA KEV**, **EPSS**, plus PoC evidence (e.g. GitHub / Packet Storm where available).

### Modes

| Mode | Use it for |
|------|------------|
| `search` | Filtered CVE list → one dataset row per CVE |
| `lookup` | Single CVE by ID (e.g. `CVE-2021-44228`) |
| `stats` | High-level corpus statistics |

### Example input (search)

```json
{
  "mode": "search",
  "q": "openssl",
  "minCvss": 7,
  "isKev": false,
  "hasPoc": true,
  "sortBy": "risk_score",
  "sortOrder": "desc",
  "limit": 20
}
```

### Pricing (pay per event)

Platform usage is included in event pricing.

| Event | When | Price |
|-------|------|-------|
| Actor start | Once per run | $0.005 |
| CVE result | Each CVE written to the dataset | $0.02 |
| Stats result | `mode=stats` payload | $0.01 |

Examples:

- 20 CVEs ≈ **$0.405** (start + 20 × $0.02)
- 100 CVEs ≈ **$2.005**
- 1,000 CVEs ≈ **$20.005**

Tip: set `limit` deliberately — you only pay for rows returned.

### Tips

- Sort by `risk_score` or `epss_score` for triage-first lists
- Combine `isKev` + `hasPoc` + `minCvss` to cut noise
- Use `publishedSince` (ISO date) for monitoring windows
- Cap with `limit` (1–250) and paginate with `offset` if needed

### Output

Results land in the default dataset (table / JSON / CSV / Excel export, or via Apify API / MCP).

# Actor input Schema

## `mode` (type: `string`):

search = filtered CVE list; lookup = single CVE id; stats = corpus stats only

## `cveId` (type: `string`):

Required when mode=lookup, e.g. CVE-2024-3094

## `q` (type: `string`):

Keyword match on id/title/description (e.g. openssl, wordpress)

## `severity` (type: `string`):

Optional severity filter. Leave empty for any severity.

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

Optional source name: nvd, cnvd, euvd, cisa.gov, github, packetstorm, epss

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

Minimum CVSS score (0-10). Leave empty for no minimum.

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

Minimum EPSS exploit probability (0-1). Leave empty for no minimum.

## `minRisk` (type: `number`):

Minimum composite risk score (0-100). Leave empty for no minimum.

## `isKev` (type: `boolean`):

If true, return only CVEs listed in CISA Known Exploited Vulnerabilities.

## `hasPoc` (type: `boolean`):

If true, return only CVEs with public PoC/exploit evidence.

## `publishedSince` (type: `string`):

Only CVEs published on/after this date, e.g. 2026-01-01

## `sortBy` (type: `string`):

Field used to sort search results.

## `sortOrder` (type: `string`):

Ascending or descending sort order.

## `limit` (type: `integer`):

Maximum number of CVEs to return (1-250). ~250 results ≈ $5 at $0.02/CVE + start fee.

## `offset` (type: `integer`):

Pagination offset for search results.

## Actor input object example

```json
{
  "mode": "search",
  "severity": "",
  "isKev": false,
  "hasPoc": false,
  "sortBy": "risk_score",
  "sortOrder": "desc",
  "limit": 20,
  "offset": 0
}
```

# Actor output Schema

## `cves` (type: `string`):

Enriched CVE records in the default dataset

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("adorable_woodworker/cerberus-cve-intel").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("adorable_woodworker/cerberus-cve-intel").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 '{}' |
apify call adorable_woodworker/cerberus-cve-intel --silent --output-dataset

```

## MCP server setup

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

```

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/eYgPcr6bcOgb2rOBS/builds/ucidzRClKTGedlBdq/openapi.json