---
title: "Return vulnerability data stored in index \"vulnerability-aliases\""
method: GET
path: "/index/vulnerability-aliases"
tags: ["indices"]
---

# Return vulnerability data stored in index "vulnerability-aliases"

`GET /index/vulnerability-aliases`

## Request

- Base URL: `https://api.vulncheck.com/v3`
- URL: `https://api.vulncheck.com/v3/index/vulnerability-aliases`
- Auth: API key in header `Authorization`
- TypeScript: <https://skmtc.dev/vulncheck/apis/vulncheck-api/docs/index/vulnerability-aliases/get.ts> (a function with typed inputs; its response is checked against the schema)

### Overview
This endpoint allows you to retrieve a paginated list of all documents from the vulnerability-aliases index. \
By default, a maximum of 100 documents are shown per page.

**Index Description:** Vulnerability Aliases

### Paging Over Large Data (cursor)
In order to allow users to iterate over large index datasets, this endpoint provides a server-side
"cursor" mechanism. To use the cursor, first call `GET /index/vulnerability-aliases?start_cursor`, the response will
have a `next_cursor` id that clients will need to pass as a query parameter to the next request like
`GET /index/vulnerability-aliases?cursor=<next_cursor_id>`

## Query parameters

- `page` integer
- `limit` integer
- `cursor` string
- `start_cursor` 'true'
- `order` 'asc' | 'desc'
- `sort` string
- `cve` string
- `alias` string
- `iava` string
- `jvndb` string
- `ilvn` string
- `threat_actor` string
- `mitre_id` string
- `misp_id` string
- `ransomware` string
- `botnet` string
- `published` string
- `date` string
- `updatedAtStartDate` string
- `updatedAtEndDate` string
- `lastModStartDate` string
- `lastModEndDate` string
- `pubStartDate` string
- `pubEndDate` string

## Response `200`

OK

- RenderResponseWithMetadataArrayApiVulnerabilityAliasPaginatePagination
  - `_benchmark` number: Benchmark is the server-side processing time for the request in seconds. Example: 0.122322 = approximately 122 milliseconds
  - `_meta` PaginatePagination: Meta is the metadata related to the endpoint response
    - `cursor` string: Cursor is an opaque string representing the current page position for cursor-based pagination. Contains encoded information about sort values and position markers. Use this value with the 'cursor' query parameter to resume pagination from this point.
    - `first_item` integer: FirstItem is the 1-indexed position of the first item on the current page. Example: Page 1 with limit 100 → FirstItem = 1 Page 2 with limit 100 → FirstItem = 101
    - `index` string: Index name being queried, corresponding to the VulnCheck data feed. Examples: "exploits", "vulncheck-nvd2", "ipintel-3d", "malicious-vscode-exts"
    - `last_item` integer: LastItem is the 1-indexed position of the last item on the current page. Accounts for partial pages. Example: Page with 50 items → LastItem = FirstItem + 49 On the final page, LastItem equals TotalRows.
    - `limit` integer: Limit is the maximum number of items returned in this response. Range: 1-100 for standard indices, 1-10 for large indices. Default: 100 (or 10 for indices marked as "large" in metadata)
    - `matches` PaginateMatch[]: Matches shows the active filter values applied to the current query. Each match includes the field name and the value being filtered on. Helps users understand which filters are currently active.
      - `field` string: Field is the name of the field being filtered on.
      - `value` string: Value is the filter value being applied to the field.
    - `max_pages` integer: MaxPages is the maximum number of pages allowed for offset-based pagination. Performance limit to prevent expensive deep pagination. Default: 6 pages. When TotalPages > MaxPages, cursor-based pagination should be used instead.
    - `next_cursor` string: NextCursor is an opaque string for fetching the next page in cursor-based pagination. When empty or null, indicates no more pages are available. More efficient than offset pagination for large datasets and real-time data.
    - `opensearch_query` object: OSQuery contains the raw OpenSearch query JSON used internally. Only included when show_query=true parameter is set. Useful for debugging complex queries and understanding performance.
    - `order` string: Order specifies the sort direction: "asc" (ascending) or "desc" (descending). Default: "desc" for most time-based indices to show newest items first.
    - `page` integer: Page is the current page number for offset-based pagination (1-indexed). First page = 1, second page = 2, etc. Used with Limit to calculate database offset. For cursor-based pagination, this field may be omitted or estimated.
    - `pages` string[]: Pages contains page numbers to display in pagination UI (e.g., [1, 2, "...", 45]). Only populated when ShowPages=true. Includes ellipsis ("...") for gaps. Limited by MaxPages to prevent overwhelming UI with too many page links.
    - `parameters` PaginateParam[]: Params describes available query parameters for this index. Each parameter includes name, format constraints, and filtering capabilities. Used for building dynamic query UIs and input validation.
      - `filtering` string: Filtering indicates the type of filtering this parameter supports. Examples: "exact", "range", "wildcard", "boolean"
      - `format` string: Format describes the expected parameter format or pattern. Examples: "CVE-YYYY-N{4-7}", "YYYY-MM-DD", "numeric"
      - `name` string: Name is the query parameter name (e.g., "cve", "date", "limit").
    - `show_pages` boolean: ShowPages controls whether the Pages array should be calculated and included. Set to true for UI pagination controls, false for API-only usage to save processing.
    - `show_query` boolean: ShowQuery indicates whether the raw OpenSearch query should be included. When true, OSQuery field will be populated with the internal query structure.
    - `sort` string: Sort field used for ordering results. Available fields vary by index. Common values: "_timestamp", "date_added", "_id", "lastSeen" Affects cursor generation and ensures pagination consistency.
    - `timestamp` string: Timestamp when the query was executed in UTC (ISO 8601 format). Used for debugging, cache management, and determining data freshness. Example: "2024-02-23T20:35:43.732591251Z"
    - `total_documents` integer: TotalRows is the total number of documents matching the query across all pages. Used for calculating total_pages and building pagination UI elements. Note: May be capped for performance on very large result sets.
    - `total_pages` integer: TotalPages is the total number of pages based on TotalRows and Limit. Calculated as: ceil(TotalRows / Limit). Used for pagination UI and validation. Example: 1000 items with limit 100 = 10 total pages.
    - `truncated` boolean: Truncated is true when a cursor page holds fewer records than Limit because it reached the response size cap, or because it would otherwise end between records that sort equally. More records follow: keep requesting with NextCursor.
    - `warnings` string[]: Warnings contains any non-fatal issues encountered during query processing. Examples: deprecated parameters, performance concerns, or data quality notes.
  - `data` ApiVulnerabilityAlias[]: Data is the data returned by the endpoint
    - `alias` string
    - `cve` string
    - `reference_url` string

## Other responses

- `404`: Not Found
- `500`: Internal Server Error

---

[API](https://skmtc.dev/vulncheck/apis/vulncheck-api.md) - [All operations](https://skmtc.dev/vulncheck/apis/vulncheck-api/llms.txt) - [OpenAPI document](https://skmtc.dev/vulncheck/apis/vulncheck-api/revisions/7c714606affe?raw)