Developer tools · Other

NVD CVE Scraper — Vulnerabilities, CVSS Scores & CWE

Search the NIST National Vulnerability Database and export CVE records — CVE ID, description, CVSS score and severity, attack vector, CWE weakness, publication dates and reference links — as clean JSON, CSV or Excel.

Run it on Apify ↗ See input & output

Free Apify credit covers a first run. No credit card to try.

What this Actor scrapes

NVD is the authoritative feed every security team watches, and it is free — but it enforces a 5-request-per-30-second limit for unauthenticated clients, buries CVSS behind three different metric schema versions, and returns each CVE with descriptions, weaknesses and references as separate nested arrays. This Actor throttles correctly, picks the newest CVSS version present, and flattens each vulnerability into one row you can sort by severity.

What we handle for you

🛡️ Browser fingerprint rotation — the target sees a real browser TLS handshake, not a script.
🌐 Proxy rotation — fresh exit on every block through Apify Proxy.
🔁 Retries with backoff — 408 / 429 / 5xx retried up to five times, Retry-After honoured.
🧊 Clean, typed rows — schema-validated output with ISO-8601 timestamps.
💰 Pay per result — no data, no result charge.

Use cases

Monitor new CVEs affecting a product or vendor in your stack.
Build a severity-ranked backlog for a patch cycle.
Feed a vulnerability dashboard without paying for a commercial feed.
Audit historical CVE exposure for a technology before adopting it.

Input

Paste this into the Apify Console, or send it as the run input over the API. Proxy settings are on by default; you rarely need to touch them.

Field	Type	Required	What it does
`keyword`	string	no	Match CVEs whose description mentions this text — a product, vendor or technology.
`cpeName`	string	no	Exact CPE 2.3 name to match, e.g. cpe:2.3:a:apache:log4j:2.14.1:::::::*. More precise than a keyword when you know the product.
`publishedFrom`	string	no	Only CVEs published on or after this date, as YYYY-MM-DD. NVD caps a publication window at 120 days, so a start date needs an end date too.
`publishedTo`	string	no	End of the publication window, as YYYY-MM-DD. Must be within 120 days of the start date.
`minCvssScore`	integer	no	Only CVEs scoring at least this (0-10). Leave at 0 for every severity. CVEs with no published score are kept.
`maxResults`	integer	no	Stop after this many CVEs. Each CVE is one billed result row.

{
  "keyword": "wordpress",
  "publishedFrom": "2026-06-01",
  "publishedTo": "2026-08-01",
  "maxResults": 3,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

Output

One row per result, schema-validated before it is written. Export JSON, CSV, Excel or XML from the run, or read it over the API.

cve_idurldescriptionvuln_statuspublishedlast_modifiedcvss_versioncvss_scorecvss_severitycvss_vectorattack_vectorcwe_idssourcereference_urls

{}

Pricing

Event	Price	When
Actor start	$0.20	Once per run, covers warm-up and proxy session setup.
Result emitted	$0.0020	Per result written to the dataset.

You pay only for results that land. Cap any run with maxTotalChargeUsd. See pricing & billing for worked examples.

Limitations

Returns NVD's published record only — no exploit code, patch status or vendor advisories.
Older CVEs often carry only a CVSS v2 score, and some carry no score at all.

FAQ

Do I need an API key?

No. The Actor stays inside NVD's unauthenticated rate limit of 5 requests per 30 seconds by throttling between pages.

Why does the date range need both ends?

NVD rejects a publication window longer than 120 days, so a start date must be paired with an end date within that span.

Which CVSS version do I get?

The newest one NVD publishes for that CVE — v3.1 where available, then v3.0, then v2.0. The <code>cvss_version</code> column always says which.

Ready to run it?

Open the listing on Apify, paste the input above, and watch rows land. If it ever breaks, it is our problem before it is yours.

Run it on Apify ↗ Ask a question

Related Actors

Teams that run this also run

$6.00/ 1k results