# NVD CVE Applicability Detail Export — CPE and CVSS (`jpmarketdata/nvd-cve-applicability-detail-export`) Actor

Refresh CVE watchlists with full CVSS metrics, CPE applicability conditions, status and advisory references for security triage and asset-matching workflows.

- **URL**: https://apify.com/jpmarketdata/nvd-cve-applicability-detail-export.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 delivered 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

## NVD CVE Applicability Detail Export

Refresh a selected CVE watchlist into complete source CVSS metrics and CPE applicability data for downstream security triage.

### Input

`cveIds` accepts 1–20 CVE identifiers. The default is `CVE-2021-44228`. Identifiers normalize to uppercase and duplicates are fetched/charged once. Blank, malformed, unknown keys, or more than 20 entries fail before requests. Every requested unique CVE must be present in NVD; unknown or not-yet-ingested identifiers fail the whole batch.

### Output

One row per unique CVE with source status, language-tagged descriptions, complete published/lastModified timestamps, every CVSS source/version array, weaknesses, all reference URLs/tags, and the full CPE applicability boolean configurations. AND/OR/negate, nested nodes, vulnerable flags and inclusive/exclusive version bounds remain intact. No affected-package claim or severity-selection shortcut is computed. Missing metrics/configurations remain empty; rejected and awaiting-analysis statuses stay visible. Metric/reference contact identifiers are normalized to their public organization domain. Each row includes official URLs, an explicit jpmarketdata derived-output label, source no-endorsement notice and modification notice. The transformed record is not presented as NVD-authored content. Source access remains documented in apiUrl and termsUrl. SUMMARY in key-value storage provides coverage/counts.

### Limits

Acquisition deadline180seconds and delivery deadline90seconds; per-request timeout30seconds. Total transfer/decoded budget64MiB; staged output24MiB. 20 input entries and 20 unique output rows; one public API `cveIds` batch query. At least 6.5 seconds between requests; 429/5xx fail explicitly without an automatic retry. NVD limits are shared by source IP across concurrent runs; avoid simultaneous schedules and rerun exhausted 429 errors later. No API key, keyword search, package scanning, exploit code, external paid service, or browser is used. Error responses, truncated coverage, unexpected duplicate/extra source identities, malformed JSON, schema changes, auth blocks, and timeout fail visibly before output.

### Pricing

One `cve-delivered` event per validated unique dataset row at $0.002; no start fee/trial events. Complete requested coverage is checked before saving rows. If the configured Apify event budget permits fewer rows than unique selected IDs, fail before requests and charges. Repeated refresh runs incur delivery events again. Duplicates, failed requests and SUMMARY are not charged.

### Privacy

Only public vulnerability information is delivered. Source contact identifiers are reduced to organization domains; no email addresses, profiles, credentials, cookies or response headers are collected. Advisory links are preserved but not fetched.

This product uses data from the NVD API but is not endorsed or certified by the NVD. NIST data is provided AS IS. Users must verify its accuracy, currency, and suitability before downstream decisions.

# Actor input Schema

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

1–20 CVE IDs. Each unique uppercase identifier becomes one detail record and one billable event. All selected identifiers must exist in the source; unsupported values fail the run.

## Actor input object example

```json
{
  "cveIds": [
    "CVE-2021-44228"
  ]
}
```

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

// Run the Actor and wait for it to finish
const run = await client.actor("jpmarketdata/nvd-cve-applicability-detail-export").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("jpmarketdata/nvd-cve-applicability-detail-export").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 jpmarketdata/nvd-cve-applicability-detail-export --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/nvd-cve-applicability-detail-export"
        }
    }
}
```

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/PTymQVxLfuov24LJD/builds/65WUCPn18wTFlP8Gd/openapi.json