NVD CVE Tracker by Vendor, Product, Severity avatar

NVD CVE Tracker by Vendor, Product, Severity

Pricing

$2.00 / 1,000 cve extracteds

Go to Apify Store
NVD CVE Tracker by Vendor, Product, Severity

NVD CVE Tracker by Vendor, Product, Severity

Pull new/modified CVEs from NIST NVD. Filter by vendor/product (CPE), severity, CWE, keyword. One row per CVE — id, description, CVSS v3 score, vector, CWEs, affected CPEs, refs. AppSec cron watchlist. NIST NVD REST 2.0 (free, no auth).

Pricing

$2.00 / 1,000 cve extracteds

Rating

0.0

(0)

Developer

vøiddo

vøiddo

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

NVD CVE Tracker — by Vendor, Product, Severity

Pull newly-published or newly-modified CVEs from NIST NVD. Filter by vendor/product (CPE 2.3), severity, CWE, or keyword. One clean row per CVE — id, description, CVSS v3 score & vector, CWEs, affected CPEs, references, NVD URL.

Built for cron: pass sinceDays: 1 for a daily AppSec watchlist of your tech stack.

Inputs

{
"keywords": ["openssl", "cisco asa"],
"cpeFilters": ["cpe:2.3:a:apache:*:*:*:*:*:*:*:*:*"],
"severityFilters": ["HIGH", "CRITICAL"],
"sinceDays": 7,
"maxResultsPerQuery": 200
}
inputdefaultnotes
keywordsFree-text searches over CVE descriptions. Each is a separate query.
cpeFiltersCPE 2.3 match strings (wildcards allowed). Each is a separate query.
severityFiltersallLimit to LOW, MEDIUM, HIGH, CRITICAL (CVSS v3).
cweIdOptional CWE filter (e.g. CWE-89).
sinceDays7lastModified >= now - sinceDays. NVD max window is 120 days.
maxResultsPerQuery200Cap per keyword/CPE query. NVD page size up to 2000.
apiKeyOptional NVD API key — boosts rate from 5/30s to 50/30s.

Output

One row per CVE (deduplicated across keyword/CPE queries):

fieldexample
cveIdCVE-2026-12345
published2026-05-30T14:00:00.000
lastModified2026-06-01T09:12:33.140
vulnStatusAnalyzed, Modified, Awaiting Analysis
descriptionIn Apache HTTP Server <2.4.62, ...
cvssV3Version3.1
cvssV3BaseScore9.1
cvssV3SeverityCRITICAL
cvssV3VectorStringCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
exploitabilityScore3.9
impactScore5.9
cwes["CWE-119", "CWE-787"]
affectedCpes["cpe:2.3:a:apache:http_server:2.4.61:*:*:*:*:*:*:*"]
references["https://www.openssl.org/news/secadv/20260530.txt", ...]
nvdUrlhttps://nvd.nist.gov/vuln/detail/CVE-2026-12345
queryOriginkw=openssl sev=CRITICAL

Daily cron pattern

{
"cpeFilters": [
"cpe:2.3:a:apache:*:*:*:*:*:*:*:*:*",
"cpe:2.3:a:nginx:*:*:*:*:*:*:*:*:*",
"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*"
],
"severityFilters": ["HIGH", "CRITICAL"],
"sinceDays": 1
}

Real-world questions this answers

  • AppSec triage. Daily firehose of HIGH+CRITICAL CVEs affecting our stack.
  • Vendor watch. Anything new from Cisco / Microsoft / Red Hat?
  • Supply-chain audit. New CVEs in a CPE-matched component.
  • Vulnerability research. Filter by CWE for class-specific datasets.

What it doesn't do

  • No EPSS / KEV enrichment yet (those are separate FIRST.org / CISA feeds; planned).
  • No vendor advisory PDFs — just NVD-stored references.
  • No exploit-availability flag (NVD doesn't expose exploit-db mapping reliably).

Maintained by

vøiddo studio — small independent shop.