POST /api/nvd/cves
Price: 5 credits
Get a CVE vulnerability record by its CVE identifier
Get the full NVD (National Vulnerability Database) record for a vulnerability by CVE id (e.g. 'CVE-2021-44228'). Returns the description, publication and last-modified dates, analysis status, CWE weakness ids, CVSS v2 / v3.0 / v3.1 / v4.0 severity metrics (vector, base score, severity, exploitability and impact sub-scores), SSVC decision points, affected vendors/products and version ranges, CPE applicability configurations, reference links with tags, vendor comments, and — when the vulnerability is in the CISA Known Exploited Vulnerabilities (KEV) catalog — the KEV exploit-added date, action due date, required action and catalog name.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)cve_id string required — CVE identifier (also accepts a nvd.nist.gov vulnerability detail URL) (examples: "CVE-2021-44228", "CVE-2024-3596"; minLength: 1)@type string (default: "NvdCve")id string requiredsource_identifier string nullablepublished_at string nullablelast_modified_at string nullablevuln_status string nullabledescription string nullablecve_tags array (default: [])evaluator_comment string nullableevaluator_solution string nullableevaluator_impact string nullablecwe_ids array (default: [])weaknesses array (default: [])@type string (default: "NvdWeakness")source string nullabletype string nullablecwe_ids array (default: [])cvss_metrics array (default: [])@type string (default: "NvdCvssMetric")version string requiredsource string nullabletype string nullablevector_string string nullablebase_score number nullablebase_severity string nullableexploitability_score number nullableimpact_score number nullableattack_vector string nullableattack_complexity string nullableattack_requirements string nullableprivileges_required string nullableuser_interaction string nullableauthentication string nullablescope string nullableconfidentiality_impact string nullableintegrity_impact string nullableavailability_impact string nullablesub_confidentiality_impact string nullablesub_integrity_impact string nullablesub_availability_impact string nullablessvc array (default: [])@type string (default: "NvdSsvc")source string nullablerole string nullableversion string nullablecomputed_at string nullableexploitation string nullableautomatable string nullabletechnical_impact string nullableconfigurations array (default: [])@type string (default: "NvdConfiguration")operator string nullablenegate boolean (default: false)nodes array (default: [])@type string (default: "NvdConfigNode")operator string nullablenegate boolean (default: false)cpe_matches array (default: [])references array (default: [])@type string (default: "NvdReference")url string requiredsource string nullabletags array (default: [])affected array (default: [])@type string (default: "NvdAffectedProduct")source string nullablevendor string nullableproduct string nullableversions array (default: [])@type string (default: "NvdAffectedVersion")version string nullablestatus string nullableversion_type string nullableless_than string nullableless_than_or_equal string nullablevendor_comments array (default: [])@type string (default: "NvdVendorComment")organization string nullabletext string nullablelast_modified string nullableis_kev boolean (default: false)cisa_exploit_add string nullablecisa_action_due string nullablecisa_required_action string nullablecisa_vulnerability_name string nullableweb_url string (default: "")422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — CVE not found Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.