cve Which vulnerabilities are actually being exploited.
384k CVE records with the two things that decide urgency: whether CISA has seen it exploited in the wild, and how likely exploitation is.
search 2 credits · free sample: log4j
What it answers
Triage by urgency
sort=epss puts the likeliest first, and the KEV flag is a field rather than a guess.
By product
Vendor and product come from CPE, so a product name narrows properly.
The advisory itself
Description, references and affected version ranges, as published.
Three calls
Straight from the gateway’s own self-description — these are the calls it suggests first.
Vulnerabilities in a product
POST /v1/cve/search {"query": "palo alto globalprotect rce"} Exploited in the wild, ranked by EPSS
POST /v1/cve/search {"query": "", "filters": {"kev": true, "severity": ["critical","high"]}, "sort": "epss"} Read one
GET /v1/cve/read/CVE-2024-3400 Narrow it — cvss_score · epss · kev · published · severity · vuln_class
What it will not do
Words, not meaning: this domain has no vectors, so give it terms rather than a sentence. Showing NVD data carries a not-endorsed notice.
- NVD data is used under its terms: any display must carry the not-endorsed notice (see the attribution field).
- kev=true means CISA confirmed exploitation in the wild; epss is FIRST's probability estimate — different things.
- severity is derived from cvss_score; the 3,347 CVEs without a score have neither.
Answered something wrong here, or missing what you came for? Send us the case
Point an agent at it
Free samples run without a key; a key takes a minute.