Search for Vulnerability entities based on a filter

Find vulnerabilities by CVSS score, risk score, exploitation status, or affected product for patch prioritization.

What this endpoint does

This endpoint searches for vulnerabilities matching specified filter criteria, returning paginated results with optional enrichment fields. It supports vulnerability-specific filters including CVSS v2 and v3 score ranges (e.g., [9.0, 10.0] for critical vulnerabilities), Recorded Future risk score ranges, risk rules from the Vulnerability Risk Rules endpoint (e.g., recentMalwareActivity for actively exploited CVEs), and CPE identifiers for affected products. Combine filters for targeted vulnerability prioritization — for example, pairing a high CVSS v3 range with an active exploitation risk rule identifies the most urgent vulnerabilities. Results are paginated with a maximum of 1,000 per page and a 10,000-result total window. For single-CVE enrichment, use the Vulnerability: Lookup endpoint instead; for bulk CVE lists filtered by risk rule, use the Vulnerability Risk List endpoint.

Response data

The response contains a data.results array of vulnerability objects, each including the enrichment fields specified by the fields parameter (consult the Enrichment: Field Attributes reference for available fields). A counts object provides returned (results in the current page) and total (total matching results up to the 10,000 window). Each result includes at minimum the entity object with the CVE identifier, internal RF ID, entity type, and NVD description. Adding risk provides the risk score, criticality label, and evidence details per triggered rule; adding aiInsights provides an AI-generated triage summary.

Paginated with offset-based pagination; limit max 1,000 and limit + from cannot exceed 1,000. Results are under data.results, with counts as a sibling of data. The limit parameter has a default value of 10. The intention is to use pagination to get further results. Though limit can be set to higher values, depending on which fields are used for enrichment, this might result in slower queries and possibly even time outs.

Query Params
string

Freetext

string

The enrichment fields requested for the entities returned. Several fields can be given as a comma separated string.

See https://docs.recordedfuture.com/reference/enrichment-field-attributes for a list of values.

enum

Annotates the response with additional metadata explaining the response data elements.

Allowed:
int32
≤ 1000

Maximum number of records returned,

int32
Defaults to 0

Offsets the pagination of the request. Note that there is a limit of returning only the top 10000 results from a search, meaning if limit plus from exceeds 10000, this will result in an Bad Request message.

string

Filters entities based on risk score, e.g. on the form [20, 80] (20 <= risk score <= 80), [20,) (20 <= risk score), or [,90) (risk score < 90). '[' and ']' are inclusive while '(' and ')' are exclusive.

string

Filters for vulnerabilities based on CVSS score (from most trusted source), e.g. on the form [8.0, 9.0] (8.0 <= CVSS score <= 9.0)

string

Filters for vulnerabilities based on CVSS v3 score, e.g. on the form [8.0, 9.0] (8.0 <= CVSS v3 score <= 9.0)

string

RF ID of affected product

string

Filters entities based on the download of the first reference which is taken into account during risk scoring of the entity. All Elasticsearch compatible date formats are valid.

string

Filters entities based on the download of the latest reference which is taken into account during risk scoring of the entity. All Elasticsearch compatible date formats are valid.

string

Filters entities based on presence in a single list. Requires the list ID, which can be found using the List API

enum

Filters for Vulnerabilities based on a single risk rule.

enum

Sorts the search according to the chosen parameter. Results are sorted before pagination.

enum

The direction of the sorting by the orderBy parameter, ascending or descending.

Allowed:
string
deprecated
string

Filters for vulnerabilities based on affected products using the CPE identifier system. This field, if used, will be validated as follows:

cpe:2.3🅰️wordpress:wordpress:4.5: - Valid. Will find all products with CPEs that start with this string, like WordPress 4.5, but also 4.5 beta3 and 4.5 rc1.

cpe:2.3🅰️wordpress:wordpress:4 - Valid. Note the lack of trailing colon. Will find products with versions starting with 4. Like 4.2, 4.2.3, 4.5.

cpe:2.3🅰️wordpress:wordpress: - Valid. Will find all known identifiers for WordPress, regardless of version.

cpe:2.3🅰️wordpress: - Invalid. Too broad, the "product" part must be defined.

Response

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json