/hackerone/cves

POST /api/hackerone/cves

Price: 5 credits

List HackerOne (hackerone.com) ranked CVE catalog entries

How to use it

List the HackerOne (hackerone.com) ranked CVE catalog used to classify vulnerability reports. Returns each CVE id with its rank, CVSS score/rating/vector, CWE, EPSS score, description, publish date, submitted report count, affected product count, per-severity report counts, products and vendors. Filter by CVE id substring.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of CVE entries to return (min: 1)
• search string nullable — Filter by CVE id substring, e.g. 'CVE-2026'

Response

• @type string (default: "HackeroneCve")
• cve_id string required
• rank integer nullable
• cvss_score number nullable
• cvss_rating string nullable
• cvss_vector string nullable
• cwe_id string nullable
• cwe_name string nullable
• epss number nullable
• description string nullable
• published_at string nullable
• reports_submitted_count integer nullable
• affected_products_count integer nullable
• severity_counts object nullable
  • @type string (default: "HackeroneCveSeverityCounts")
  • critical integer nullable
  • high integer nullable
  • medium integer nullable
  • low integer nullable
  • none integer nullable
  • unknown integer nullable
• products array (default: [])
• vendors 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.