Look up a CVE
get_cveOne CVE by id: description, severity, CVSS score and vector, EPSS exploitation probability, CISA KEV status (date added, due date, required action, known ransomware use), exploitation evidence where recorded (CISA SSVC none/poc/active, Exploit-DB ids, Nuclei template, the number of Metasploit modules, Microsoft's exploited flag), affected packages with introduced and fixed versions (OSV.dev, first 5), vendor advisories (CSAF, first 3), external identifiers (GHSA, PYSEC, GO, EUVD ids, bundle advisories such as USN or RHSA, first 6), the products the CNA itself declares affected in the CVE record with their version ranges (often the only product data before NVD analyses a CVE; as many as fit), publication dates and references (NVD, KEV, EPSS, CERT-FR, GitHub advisories, Exploit-DB), and an attribution block: MITRE's CVE designation and licence and the NVD notice, to keep with any CVE text you reproduce, and the sources the answer draws on. Also takes an external id (GHSA-…, PYSEC-…, GO-…, RUSTSEC-…, EUVD-…, USN-…, RHSA-…, ALSA-…, a Metasploit module path…): one CVE comes back as its record with resolvedFrom, several as a list of candidate CVE ids to look up. No recorded exploitation evidence does not mean the CVE is not exploited. This is the only CVE lookup path; do not guess other routes. Costs one request of the monthly quota.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | CVE identifier, e.g. CVE-2021-44228, or an external id naming it, e.g. GHSA-jfh8-c2jp-5v3q, PYSEC-2021-101, EUVD-2025-1234, USN-7000-1. Case-insensitive. |