VUvulnerability-lookup
vulnerability

Get the sighting correlations of a vulnerability

Changed on

The vulnerabilities sighted by the same sources as this one: for every source that filed a sighting of it (under either spelling of a CVE), the other vulnerabilities that source filed sightings of, most sighted first. Sources are matched exactly and counted over every sighting they filed; they come most correlated first (most related vulnerabilities, then most sightings of this one, then most recent), so the caps keep the strongest relationships. The Sighting correlations graph of the vulnerability page draws this document.

get/vulnerability/{vulnerability_id}/correlations

Request

  • Base URL
    /api (relative, and the document was published on a file host, not at the API’s origin)
  • URL
    /api/vulnerability/{vulnerability_id}/correlations
  • Auth
    API key in header X-API-KEY

Query parameters

sourcesinteger

Sources listed, most correlated first (1 to 200).

per_sourceinteger

Related vulnerabilities listed per source, most sighted first (1 to 200).

Response

Success.

metadataobject

vulnerability: the id served; sources: the sources of its sightings; shown_sources: how many data holds; per_source: the cap on related vulnerabilities per source.

Example response

{
  "data": [
    {
      "seen": "2026-10-12T12:00:00Z",
      "source": "https://example.org/report",
      "type": "seen",
      "vulnerabilities": [
        "CVE-2026-0001"
      ]
    }
  ],
  "metadata": {
    "per_source": 20,
    "shown_sources": 3,
    "sources": 3,
    "vulnerability": "CVE-2026-1234"
  }
}

Changes