/cisa/vulnerabilities/search

POST /api/cisa/vulnerabilities/search

Price: 20 credits

Search the CISA Known Exploited Vulnerabilities catalog by vendor, product, weakness and dates

How to use it

Use this to answer 'which known-exploited vulnerabilities affect X' and 'what is overdue for remediation', not to look up one CVE. Every filter matches the catalog entry's own wording, so pass the vendor as CISA writes it ('Microsoft', 'Apache') rather than a legal name, and use query for anything you would otherwise guess at. An empty list means nothing in the catalog matches, not that the products are unaffected by anything.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Free-text match against the CVE id, the entry name, its short description, the vendor and the product (examples: "log4j", "remote code execution")
• vendor string nullable — Vendor or project of the affected software (examples: "Microsoft", "Apache")
• product string nullable — Affected product (examples: "Windows", "Log4j2")
• cwe_id string nullable — CWE weakness id the entry is classified under (examples: "CWE-502")
• ransomware_use string nullable — Whether CISA has linked the vulnerability to a ransomware campaign (one of: "known", "unknown")
• has_forensic_triage boolean nullable — Whether CISA flags the entry for forensic triage
• added_from string nullable — Earliest date the entry was added to the catalog (examples: "2024-01-01")
• added_to string nullable — Latest date the entry was added to the catalog (examples: "2024-12-31")
• due_from string nullable — Earliest remediation due date (examples: "2026-01-01")
• due_to string nullable — Latest remediation due date (examples: "2026-12-31")
• sort string — Order of the returned entries (default: "added_newest"; one of: "added_newest", "added_oldest", "due_soonest", "due_latest")
• count integer required — Max result count (examples: 20; min: 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 entity was not found, or a precondition failed 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.