# CISA KEV Radar — Exploited CVE Alerts (`ka1tetsu/vivlica-cisa-kev-radar`) Actor

Official CISA exploited-vulnerability catalog filtered by vendor and date, with recommended defensive remediation references.

- **URL**: https://apify.com/ka1tetsu/vivlica-cisa-kev-radar.md
- **Developed by:** [Takahashi Kiseki](https://apify.com/ka1tetsu) (community)
- **Categories:** Business, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.01 / result

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

## CISA KEV Exploited Vulnerability Radar — Defensive Patch Intelligence

Track newly listed CVEs in the **official CISA Known Exploited Vulnerabilities** catalog. Returns date added, vendor, product, publicly documented vulnerability title, known ransomware linkage, agency due date and CISA recommended remediation. Stable CVEs and `excludeCves` help security teams detect new entries since their last successful scan.

Original feed: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (JSON release). Metadata only; **no exploit code, scanning or intrusion**. CISA due dates apply to covered federal agencies and must not be treated as universal legal deadlines. These data are not a customer-specific breach diagnosis.

**Buyers:** managed security providers, defensive IT operations and supply-chain risk analysts. Prefer truthful source dates, no ML-generated severity labels. The official feed is free; the value proposition is filtering and repeatable automation. See the current Apify Pricing tab for the live rate.

### Example: daily known-exploited CVE monitoring for defensive patch teams

Use the **CISA Known Exploited Vulnerabilities API** data to automate new-CVE triage with documented CVE IDs and CISA source links.

```json
{"daysBack":90,"maxResults":50,"vendorKeywords":[],"knownRansomwareOnly":false}
```

Fields include `cve`, `dateAdded`, `vendor`, `product`, `requiredAction`, `dueDate` and `sourceUrl`. To monitor only new records, store returned CVE IDs and send them back as `excludeCves`. For ransomware-related catalog flags, set `knownRansomwareOnly` to true. Empty output can mean no matching records; it does not prove your assets are free of vulnerabilities.

#### Automated workflows

Run the Actor on a schedule, use the dataset JSON in your patch-management or security engineering workflow, and independently verify the affected versions against vendor guidance. You can call it through Apify API or an AI agent using Apify's integrations.

#### Pricing

Check the live **Pricing** tab for the actual customer charge before running. The official CISA feed is public; you pay for a bounded, repeatable and structured aggregation service, not for exclusivity or the underlying public data. This is a defensive intelligence product, never a vulnerability exploit or live scan.

# Actor input Schema

## `daysBack` (type: `integer`):

Days from today to consider newly added known-exploited CVEs.

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

Limit delivered vulnerability metadata events.

## `vendorKeywords` (type: `array`):

Optional targeted software/hardware vendors, max 8.

## `knownRansomwareOnly` (type: `boolean`):

Restrict to records marked Known by CISA for ransomware campaigns.

## `excludeCves` (type: `array`):

Exclude known CVE identifiers from earlier runs.

## Actor input object example

```json
{
  "daysBack": 90,
  "maxResults": 100,
  "vendorKeywords": [],
  "knownRansomwareOnly": false,
  "excludeCves": []
}
```

# Actor output Schema

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

No description

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

// Run the Actor and wait for it to finish
const run = await client.actor("ka1tetsu/vivlica-cisa-kev-radar").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("ka1tetsu/vivlica-cisa-kev-radar").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 ka1tetsu/vivlica-cisa-kev-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ka1tetsu/vivlica-cisa-kev-radar"
        }
    }
}
```

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/TI3qyhLIuaqjyZhje/builds/sQFEd2JPtB8bxX2IA/openapi.json