Issues API — Vulnerability category on issues

Each issue in the issues list now includes the category of its underlying vulnerability, so you no longer need to look it up separately when routing issues to the right team or ticket queue.

Endpoint: GET /v1/issues/

• vulnerability_category — The category name of the underlying vulnerability, for example Attack Surface Reduction. May be null if the vulnerability has no category name set.

Issues API — Filter by exploit likelihood

Issues can now be filtered by how likely the underlying vulnerability is to be exploited. This matches the exploit likelihood already returned on each issue, which is based on the highest EPSS score across the issue's occurrences, with a known exploit taking precedence.

Endpoint: GET /v1/issues/

• exploit_likelihood (optional) — One of: known, very_likely, likely, unlikely, rare, unknown. Use unknown to find issues with no EPSS score — these return exploit_likelihood as null.

Issues API — Filter by vulnerability category

Issues can now be filtered by the category of the underlying vulnerability, so you can pull just one class of finding.

Endpoint: GET /v1/issues/

• vulnerability_categories (optional) — Comma-separated vulnerability category names, for example Attack Surface Reduction,Advisories. Names are matched exactly, but are not case sensitive.

For more information, see the API documentation for issues.