# CVElens Vulnerability Intelligence (`dweissbacher/cvelens-vulnerability-intelligence`) Actor

One record per CVE: NVD data and CVSS, CISA KEV status, EPSS exploit probability, public exploit code (Exploit-DB, Metasploit, Nuclei) and an explained 0-100 risk score. Look up ids, search by vendor/severity/KEV/EPSS, list recent KEV additions or the top EPSS scores.

- **URL**: https://apify.com/dweissbacher/cvelens-vulnerability-intelligence.md
- **Developed by:** [Daniel Weißbacher](https://apify.com/dweissbacher) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 cve records

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

## CVElens Vulnerability Intelligence

One record per CVE with everything you need to decide whether it matters:

- **NVD**: description, CVSS v4 / v3.1 / v3.0 / v2 with vectors, CWE, affected vendors and products
- **CISA KEV**: known-exploited status, date added, remediation due date, known ransomware use
- **EPSS** (FIRST.org): probability of exploitation within 30 days, with percentile, updated daily
- **Public exploits**: Exploit-DB entries, Metasploit modules and Nuclei templates, with links
- **Risk score**: 0 to 100 with every contributing factor listed, so you can explain a priority

Served from a continuously synced mirror of 390,000+ CVEs. Complete where NVD is not: KEV, EPSS
and exploit data are present even for CVEs NVD has not scored yet, and those say `unscored`
instead of pretending to be low risk.

### Modes

| Mode | What you get | Inputs |
|---|---|---|
| **Look up CVE ids** | One record per id, up to 1,000 per run | `cveIds` |
| **Search and filter** | Records matching your filters, newest first by default | `vendor`, `product`, `kevOnly`, `exploitOnly`, `epssMin`, `cvssMin`, `severity`, `cwe`, `publishedSince`, `modifiedSince`, `query`, `sort`, `maxItems` |
| **Recent CISA KEV additions** | The KEV catalog, newest first | `publishedSince` (added since), `vendor`, `ransomwareOnly`, `maxItems` |
| **Top EPSS scores** | Highest exploit probabilities | `excludeKev`, `maxItems` (up to 200) |

#### Examples

*Which Cisco CVEs are being exploited and have public exploit code, worst first?*
Mode: search · vendor `cisco` · kevOnly · exploitOnly · sort `epss`.

*Everything CISA added this week:* Mode: kev · publishedSince `2026-09-15`.

*What is likely to be exploited next but not yet in KEV:* Mode: epss\_top · excludeKev · maxItems 100.

*Enrich my scanner's findings:* Mode: lookup · paste the ids.

### Output

Each dataset row is one CVE, flat columns first so the table view is scannable, then the full
nested record:

```json
{
  "id": "CVE-2021-44228",
  "risk_score": 100,
  "risk_level": "critical",
  "cvss_score": 10.0,
  "cvss_severity": "CRITICAL",
  "cvss_version": "3.1",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.99999,
  "epss_percentile": 1.0,
  "kev_listed": true,
  "kev_date_added": "2021-12-10",
  "kev_due_date": "2021-12-24",
  "kev_ransomware": "Known",
  "exploit_count": 9,
  "exploit_sources": ["exploitdb", "metasploit", "nuclei"],
  "published": "2021-12-10",
  "last_modified": "2026-08-11",
  "status": "Analyzed",
  "vendors": "apache, apple, cisco, debian, ...",
  "cwe": ["CWE-20", "CWE-400", "CWE-502", "CWE-917"],
  "description": "Apache Log4j2 2.0-beta9 through 2.15.0 ...",
  "risk_factors": [{"factor": "cvss_v3.1", "value": 10.0, "points": 50}, {"factor": "epss", "value": 0.99999, "points": 25}, {"factor": "cisa_kev", "value": "ransomware", "points": 20}, {"factor": "public_exploit", "value": ["exploitdb", "metasploit", "nuclei"], "points": 10}],
  "cvss_all": {"v4": null, "v3_1": {"score": 10.0, "...": "..."}, "v2": {"score": 9.3, "...": "..."}},
  "kev": {"vendor_project": "Apache", "product": "Log4j2", "required_action": "...", "...": "..."},
  "exploits": [{"source": "metasploit", "ref": "exploit/multi/http/log4shell_header_injection", "url": "https://github.com/rapid7/...", "verified": true}],
  "affected_products": [{"vendor": "apache", "product": "log4j"}],
  "cpe_count": 373,
  "found": true
}
```

Ids that exist in no source are pushed as `{"id": "...", "found": false}` and are not charged.
`includeReferences` adds the NVD reference URLs; `includeCpes` adds up to 50 CPE match strings.

### Risk score

| Factor | Points |
|---|---|
| Best available CVSS base score | 0 to 50 (score / 10 × 50) |
| EPSS probability | 0 to 25 (epss × 25) |
| Listed in CISA KEV | +15, or +20 with known ransomware use |
| Public exploit code | +10 for Metasploit or Exploit-DB, +5 for Nuclei template only |

Capped at 100. Levels: critical ≥ 80, high ≥ 60, medium ≥ 35, low otherwise, and `unscored`
when no source has anything yet.

### Pricing

Pay per event: each CVE record returned is one `cve-record` event. Records not found are free.
Use `maxItems` to cap a run, or the run's maximum total charge in Apify; the Actor stops
cleanly at the limit and keeps what it already fetched.

### Use with AI agents

Every Apify Actor is available as a tool through the Apify MCP server, so you can ask an agent
"which Cisco CVEs in KEV have public exploit code, ranked by EPSS?" and it will call this Actor.
The same data is also available directly as a REST API and a first-party MCP endpoint at
[api.cvelens.com](https://api.cvelens.com/docs), also on [RapidAPI](https://rapidapi.com/danielweissbacher1997/api/cvelens-vulnerability-intelligence).

### Data sources and freshness

NIST NVD (continuous, by modification date) · CISA KEV (hourly, CC0) · FIRST EPSS (hourly; scores
update daily) · Exploit-DB, Rapid7 Metasploit, ProjectDiscovery Nuclei (hourly). CVElens is not
affiliated with any of these organisations. Risk scores are informational and do not replace
your own assessment.

Questions: support@cvelens.com

# Changelog

This Actor's version history is a separate document: https://apify.com/dweissbacher/cvelens-vulnerability-intelligence/changelog.md

# Actor input Schema

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

lookup: records for the CVE ids you list. search: filter the whole database. kev: CISA Known Exploited Vulnerabilities, newest first. epss\_top: highest exploit-probability CVEs.

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

One CVE id per line, e.g. CVE-2021-44228. Up to 1,000 per run.

## `vendor` (type: `string`):

NVD CPE vendor name in lower case, e.g. microsoft, apache, cisco.

## `product` (type: `string`):

NVD CPE product name in lower case, e.g. windows\_10, log4j, ios.

## `kevOnly` (type: `boolean`):

Search mode: keep only CVEs CISA lists as known exploited.

## `exploitOnly` (type: `boolean`):

Search mode: keep only CVEs with an Exploit-DB entry, Metasploit module or Nuclei template.

## `epssMin` (type: `string`):

0 to 1, e.g. 0.5 for a 50% probability of exploitation within 30 days.

## `cvssMin` (type: `string`):

0 to 10, best available CVSS version.

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

Best available CVSS severity.

## `cwe` (type: `string`):

e.g. CWE-79

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

ISO date, e.g. 2026-01-01. In KEV mode: entries added since this date.

## `modifiedSince` (type: `string`):

ISO date or datetime, e.g. 2026-09-01T00:00:00. Useful for polling changes.

## `query` (type: `string`):

Words that must all appear in the description. Append \* for a prefix, e.g. deserial\*.

## `sort` (type: `string`):

Search mode ordering, descending.

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

KEV mode: keep only entries CISA marks with known ransomware campaign use.

## `excludeKev` (type: `boolean`):

Hide CVEs CISA already lists, to surface what is likely to be exploited next.

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

Upper bound on records returned (and charged) in search, KEV and EPSS modes.

## `includeReferences` (type: `boolean`):

Add the NVD reference list (advisories, patches) to each record. Larger output.

## `includeCpes` (type: `boolean`):

Add up to 50 vulnerable CPE strings per record. Larger output.

## Actor input object example

```json
{
  "mode": "lookup",
  "cveIds": [
    "CVE-2021-44228",
    "CVE-2024-3094",
    "CVE-2023-4863"
  ],
  "kevOnly": false,
  "exploitOnly": false,
  "severity": "",
  "sort": "modified",
  "ransomwareOnly": false,
  "excludeKev": false,
  "maxItems": 100,
  "includeReferences": false,
  "includeCpes": false
}
```

# Actor output Schema

## `records` (type: `string`):

All CVE records from this run as JSON. Add ?format=csv for a spreadsheet.

## `overview` (type: `string`):

Only the scannable columns: id, risk\_score, risk\_level, cvss\_score, cvss\_severity, epss\_score, kev\_listed, kev\_ransomware, exploit\_count, published, vendors, 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 = {
    "mode": "lookup",
    "cveIds": [
        "CVE-2021-44228",
        "CVE-2024-3094",
        "CVE-2023-4863"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dweissbacher/cvelens-vulnerability-intelligence").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 = {
    "mode": "lookup",
    "cveIds": [
        "CVE-2021-44228",
        "CVE-2024-3094",
        "CVE-2023-4863",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("dweissbacher/cvelens-vulnerability-intelligence").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 '{
  "mode": "lookup",
  "cveIds": [
    "CVE-2021-44228",
    "CVE-2024-3094",
    "CVE-2023-4863"
  ]
}' |
apify call dweissbacher/cvelens-vulnerability-intelligence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dweissbacher/cvelens-vulnerability-intelligence"
        }
    }
}
```

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/u6nBy23qauPsZIIPQ/builds/5icbSuR2CxZWoDwub/openapi.json
