/cisa/vulnerabilities

POST /api/cisa/vulnerabilities

Price: 20 credits

Get a CISA Known Exploited Vulnerabilities catalog entry by CVE id

How to use it

Answers whether CISA has recorded a CVE as actively exploited in the wild, and what US federal agencies are ordered to do about it by when. Pass the CVE id in any text containing it, including a full sentence or an NVD URL. Absence from the catalog is a finding about the vulnerability, not a gap in the lookup, so read it as 'CISA has not recorded exploitation' rather than as unknown. `notes` here is a single ';'-separated string, unlike ics_advisories and CSAF vulnerabilities on this platform where `notes` is a list of structured objects — this endpoint's KEV source ships it as one string.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• cve_id string required — CVE identifier of the catalog entry (examples: "CVE-2021-44228", "CVE-2024-3400"; minLength: 1)

Response

• @type string (default: "CisaKevVulnerability")
• id string required
• name string nullable
• vendor string nullable
• product string nullable
• description string nullable
• required_action string nullable
• added_date string nullable
• due_date string nullable
• known_ransomware_campaign_use string nullable
• has_forensic_triage boolean nullable
• cwe_ids array (default: [])
• notes string nullable
• note_urls array (default: [])

Errors

• 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 — The CVE is not in the CISA Known Exploited Vulnerabilities catalog. 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.