# Vulnerability-Lookup

> Look up vulnerabilities in CIRCL's Vulnerability-Lookup, which gathers the CVE list, NVD, GitHub and OSV advisories, vendor advisories and CERT bulletins: get any vulnerability in plain fields with its severity, EPSS score and exploited status, watch a product or source for new ones, search, browse vendors and products, and read CWEs, sightings and detection rules. No account needed.

App · 20 actions. Web page: https://docs.lodol.com/docs/integrations/vulnerability-lookup

## Actions

### Get attack pattern (CAPEC)

Look up an attack pattern in MITRE's CAPEC list, such as CAPEC-66 (SQL injection): how the attack works step by step, what it needs, its severity, how to defend against it and the weaknesses it exploits.

**Inputs**

- CAPEC (`capec_id`, text, required): The attack pattern's id, such as CAPEC-66 or 66.

**Outputs**

- `abstraction` (text): How general it is: Meta, Standard or Detailed.
- `consequences` (list): What an attacker gains: 'Scope: impact'.
- `description` (text): What the attack is.
- `execution_flow` (list): The attack's steps: 'Phase: what happens'.
- `extended_description` (text): More detail, when MITRE gives it.
- `found` (true/false): False when there is no such attack pattern.
- `id` (text): The attack pattern's id, e.g. CAPEC-66.
- `likelihood_of_attack` (text): How likely the attack is, e.g. High.
- `mitigations` (list): Ways to defend against it, up to ten.
- `name` (text): The attack pattern's name.
- `prerequisites` (list): What the attack needs to work.
- `related_attack_patterns` (list): Related attack patterns.
- `related_weaknesses` (list): The weaknesses it exploits, e.g. CWE-89.
- `skills_required` (list): The skill an attacker needs.
- `status` (text): MITRE's status for the entry, e.g. Draft.
- `summary` (text): One line describing the result.
- `typical_severity` (text): How severe it usually is, e.g. High.
- `url` (text): The attack pattern's page on capec.mitre.org.

**Example output**

```json
{
  "abstraction": "Standard",
  "consequences": [
    "Integrity: Modify Data"
  ],
  "description": "This attack exploits target software that constructs SQL statements based on user input.",
  "execution_flow": [
    "Explore: [Survey application] The attacker first takes an inventory of the functionality exposed by the application."
  ],
  "extended_description": null,
  "found": true,
  "id": "CAPEC-66",
  "likelihood_of_attack": "High",
  "mitigations": [
    "Strong input validation."
  ],
  "name": "SQL Injection",
  "prerequisites": [
    "SQL queries used by the application to store, retrieve or modify data."
  ],
  "related_attack_patterns": [
    "CAPEC-248"
  ],
  "related_weaknesses": [
    "CWE-89",
    "CWE-1286"
  ],
  "skills_required": [
    "It is fairly simple for someone with basic SQL knowledge to perform SQL injection, in general."
  ],
  "status": "Draft",
  "summary": "CAPEC-66: SQL Injection",
  "typical_severity": "High",
  "url": "https://capec.mitre.org/data/definitions/66.html"
}
```

### Get EPSS score

Get a CVE's EPSS score: FIRST's daily estimate of the chance it is exploited in the next 30 days, and how that ranks among all CVEs. Useful for deciding what to patch first.

**Inputs**

- CVE (`cve_id`, text, required): The CVE id, such as CVE-2021-44228.

**Outputs**

- `cve_id` (text): The CVE.
- `date` (text): The day the score was computed.
- `epss_percent` (number): The same chance as a percentage.
- `epss_score` (number): The chance of exploitation in 30 days, 0 to 1.
- `found` (true/false): False when the CVE has no EPSS score.
- `percentile` (number): How it ranks among all CVEs, 0 to 1.
- `summary` (text): One line describing the result.

**Example output**

```json
{
  "cve_id": "CVE-2021-44228",
  "date": "2026-10-19",
  "epss_percent": 99.999,
  "epss_score": 0.99999,
  "found": true,
  "percentile": 1.0,
  "summary": "CVE-2021-44228: 99.999% chance of exploitation in the next 30 days, higher than 100% of CVEs"
}
```

### Get known-exploited status

Check whether a vulnerability is known to be exploited in the wild, across every known-exploited (KEV) catalog Vulnerability-Lookup gathers, such as CISA's, Shadowserver's and its own, with each catalog's notes.

**Inputs**

- Vulnerability ID (`vulnerability_id`, text, required): A vulnerability id such as CVE-2021-44228, GHSA-jfh8-c2jp-5v3q or PYSEC-2021-19. A vulnerability page's address works too.

**Outputs**

- `catalogs` (list): The catalogs that list it as exploited.
- `count` (number): How many catalog entries there are.
- `entries` (list): Each catalog's entry.
- `known_exploited` (true/false): True when any catalog lists it as exploited.
- `summary` (text): One line describing the result.
- `vulnerability_id` (text): The vulnerability checked.

**Example output**

```json
{
  "catalogs": [
    "cisa-kev"
  ],
  "count": 1,
  "entries": [
    {
      "catalog": "cisa-kev",
      "catalog_name": "CISA Known Exploited Vulnerabilities Catalog",
      "exploited": true,
      "first_seen": "2021-12-10T00:00:00+00:00",
      "last_seen": null,
      "notes": "KEV entry: Apache Log4j2 Remote Code Execution Vulnerability | Due date: 2021-12-24",
      "status_reason": "confirmed",
      "status_updated": "2021-12-10T00:00:00+00:00",
      "vulnerability_id": "CVE-2021-44228"
    }
  ],
  "known_exploited": true,
  "summary": "CVE-2021-44228 is known to be exploited, according to 1 catalog (cisa-kev)",
  "vulnerability_id": "CVE-2021-44228"
}
```

### Get vendor VEX statements

Get what vendors such as Red Hat and SUSE say about a vulnerability in their VEX statements: their severity, and how many of their products are fixed, affected or not affected.

**Inputs**

- Vulnerability ID (`vulnerability_id`, text, required): A vulnerability id such as CVE-2021-44228, GHSA-jfh8-c2jp-5v3q or PYSEC-2021-19. A vulnerability page's address works too.

**Outputs**

- `count` (number): How many are listed here.
- `statements` (list): Each vendor's statement.
- `summary` (text): One line describing the result.
- `vulnerability_id` (text): The vulnerability.

**Example output**

```json
{
  "count": 1,
  "statements": [
    {
      "first_released": "2021-12-10T02:01:00+00:00",
      "fixed": 122,
      "known_affected": 4,
      "known_not_affected": 2254,
      "last_updated": "2026-09-11T13:45:16+00:00",
      "recommended": null,
      "severity": "critical",
      "status": "final",
      "title": "log4j-core: Remote code execution in Log4j 2.x",
      "under_investigation": null,
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2021/cve-2021-44228.json",
      "vendor": "Red Hat CSAF VEX",
      "version": "3"
    }
  ],
  "summary": "CVE-2021-44228: 1 VEX statement (Red Hat CSAF VEX)",
  "vulnerability_id": "CVE-2021-44228"
}
```

### Get vulnerability

Look up one vulnerability by its id (CVE, GitHub advisory, PyPI, Red Hat and many more) and get it in plain fields: title, description, severity and CVSS score, weaknesses (CWEs), affected products and versions, references, its EPSS chance of being exploited and whether CISA lists it as known exploited. Unknown ids come back with 'found' set to false.

**Inputs**

- Vulnerability ID (`vulnerability_id`, text, required): A vulnerability id such as CVE-2021-44228, GHSA-jfh8-c2jp-5v3q or PYSEC-2021-19. A vulnerability page's address works too.

**Outputs**

- `affected` (list): The affected products and versions.
- `aliases` (list): Other ids for the same vulnerability, e.g. its CVE.
- `assigner` (text): Who assigned the id, e.g. apache or GitHub.
- `cvss_score` (number): The CVSS base score, 0 to 10, when rated.
- `cvss_vector` (text): The CVSS vector, e.g. CVSS:3.1/AV:N/AC:L/...
- `cvss_version` (text): The CVSS version of that score, e.g. 3.1.
- `cwes` (list): The weaknesses behind it, e.g. CWE-502.
- `description` (text): What the vulnerability is, in the source's words.
- `epss_percentile` (number): How the EPSS score ranks among all CVEs, 0 to 1.
- `epss_score` (number): FIRST's EPSS estimate, 0 to 1, that the CVE is exploited in the next 30 days.
- `format` (text): The record's format: cve, osv, nvd, csaf or other.
- `found` (true/false): False when Vulnerability-Lookup has no record with this id.
- `id` (text): The vulnerability's id, e.g. CVE-2021-44228 or GHSA-jfh8-c2jp-5v3q.
- `kev_date_added` (text): When CISA added it to that catalog.
- `kev_due_date` (text): CISA's deadline for US federal agencies to fix it.
- `kev_required_action` (text): What CISA says to do about it.
- `known_exploited` (true/false): True when CISA's Known Exploited Vulnerabilities catalog lists the CVE; empty for ids that are not CVEs.
- `known_ransomware_use` (text): Whether ransomware campaigns use it: Known or Unknown.
- `published` (text): When the record was published (ISO 8601).
- `references` (list): Links to advisories, fixes and write-ups.
- `severity` (text): critical, high, medium, low or none, when rated.
- `source` (text): The Vulnerability-Lookup source the record came from, e.g. cvelistv5 or github, when known.
- `state` (text): The record's state, e.g. PUBLISHED or REJECTED, when given.
- `summary` (text): One line describing the result.
- `title` (text): The record's title, when it has one.
- `updated` (text): When the record was last updated (ISO 8601).
- `url` (text): Its page on vulnerability.circl.lu.

**Example output**

```json
{
  "affected": [
    {
      "product": "Apache Log4j2",
      "vendor": "Apache Software Foundation",
      "versions": "2.0-beta9 and later, except from 2.3.1, 2.12.2, 2.15.0"
    }
  ],
  "aliases": [],
  "assigner": "apache",
  "cvss_score": 10.0,
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "cvss_version": "3.1",
  "cwes": [
    "CWE-502",
    "CWE-400",
    "CWE-20"
  ],
  "description": "Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints.",
  "epss_percentile": 1.0,
  "epss_score": 0.99999,
  "format": "cve",
  "found": true,
  "id": "CVE-2021-44228",
  "kev_date_added": "2021-12-10",
  "kev_due_date": "2021-12-24",
  "kev_required_action": "For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks.",
  "known_exploited": true,
  "known_ransomware_use": "Known",
  "published": "2021-12-10T00:00:00.000Z",
  "references": [
    "https://logging.apache.org/log4j/2.x/security.html"
  ],
  "severity": "critical",
  "source": null,
  "state": "PUBLISHED",
  "summary": "CVE-2021-44228 (critical, CVSS 10.0): Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints [known exploited]",
  "title": "Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints",
  "updated": "2025-10-21T23:25:23.121Z",
  "url": "https://vulnerability.circl.lu/vuln/CVE-2021-44228"
}
```

### Get weakness (CWE)

Look up a software weakness in MITRE's CWE list, such as CWE-79 (cross-site scripting): what it is, its consequences, how to prevent it, related weaknesses and attack patterns, and real vulnerabilities it caused.

**Inputs**

- CWE (`cwe_id`, text, required): The weakness's id, such as CWE-79 or 79.

**Outputs**

- `abstraction` (text): How general it is: Pillar, Class, Base or Variant.
- `alternate_terms` (list): Other names for it, e.g. XSS.
- `consequences` (list): What an attacker gains: 'Scope: impact'.
- `description` (text): What the weakness is.
- `extended_description` (text): More detail, when MITRE gives it.
- `found` (true/false): False when there is no such weakness.
- `id` (text): The weakness's id, e.g. CWE-79.
- `likelihood_of_exploit` (text): How likely it is to be exploited, e.g. High.
- `mitigations` (list): Ways to prevent it, up to ten: 'Phase: advice'.
- `name` (text): The weakness's name.
- `observed_examples` (list): Real vulnerabilities it caused, up to ten.
- `related_attack_patterns` (list): Attack patterns that use it, e.g. CAPEC-63.
- `related_weaknesses` (list): Related weaknesses, e.g. CWE-74.
- `status` (text): MITRE's status for the entry, e.g. Stable.
- `summary` (text): One line describing the result.
- `url` (text): The weakness's page on cwe.mitre.org.

**Example output**

```json
{
  "abstraction": "Base",
  "alternate_terms": [
    "XSS"
  ],
  "consequences": [
    "Access Control, Confidentiality: Bypass Protection Mechanism, Read Application Data"
  ],
  "description": "The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.",
  "extended_description": null,
  "found": true,
  "id": "CWE-79",
  "likelihood_of_exploit": "High",
  "mitigations": [
    "Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur."
  ],
  "name": "Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')",
  "observed_examples": [
    {
      "description": "XSS in AI assistant",
      "reference": "CVE-2024-49038"
    }
  ],
  "related_attack_patterns": [
    "CAPEC-63"
  ],
  "related_weaknesses": [
    "CWE-74"
  ],
  "status": "Stable",
  "summary": "CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')",
  "url": "https://cwe.mitre.org/data/definitions/79.html"
}
```

### List bundles

List bundles: write-ups that group related vulnerabilities, such as those in one campaign or report. Filter by a vulnerability they mention, author and dates.

**Inputs**

- Vulnerability ID (`vulnerability_id`, text): Only those about this vulnerability, e.g. CVE-2021-44228. Leave empty for all.
- Author (`author`, text): Only those by this Vulnerability-Lookup user (their login).
- From (`date_from`, date): Only those on or after this day.
- To (`date_to`, date): Only those on or before this day.
- Page (`page`, number): Which page to return, 1 first. From 1 to 100000.
- Per page (`per_page`, number): How many to return, 1 to 1000. Defaults to 20 (100 for sightings). From 1 to 1000.

**Outputs**

- `bundles` (list): The bundles, newest first.
- `count` (number): How many are listed here.
- `page` (number): The page returned, 1 first.
- `per_page` (number): The page size asked for.
- `summary` (text): One line describing the result.
- `total` (number): How many match in all, across every page, when the API says.

**Example output**

```json
{
  "bundles": [
    {
      "author": "C\u00e9dric Bonhomme",
      "created": "2025-03-11T20:37:58.600981+00:00",
      "description": "The fourth edition of the Cyber Threat Overview.",
      "name": "Cyber Threat Overview 2024 from CERT-FR",
      "updated": "2025-03-11T20:42:51.574321+00:00",
      "url": "https://vulnerability.circl.lu/bundle/11268897-8798-4ec2-bcac-b23fe0715823",
      "uuid": "11268897-8798-4ec2-bcac-b23fe0715823",
      "vulnerabilities": [
        "CVE-2024-21762"
      ]
    }
  ],
  "count": 1,
  "page": 1,
  "per_page": 20,
  "summary": "2 bundles mentioning CVE-2024-21762",
  "total": 2
}
```

### List comments

List the comments analysts have left on vulnerabilities, such as notes on exploitation or mitigation, newest first. Filter by vulnerability, author and dates.

**Inputs**

- Vulnerability ID (`vulnerability_id`, text): Only those about this vulnerability, e.g. CVE-2021-44228. Leave empty for all.
- Author (`author`, text): Only those by this Vulnerability-Lookup user (their login).
- From (`date_from`, date): Only those on or after this day.
- To (`date_to`, date): Only those on or before this day.
- Page (`page`, number): Which page to return, 1 first. From 1 to 100000.
- Per page (`per_page`, number): How many to return, 1 to 1000. Defaults to 20 (100 for sightings). From 1 to 1000.

**Outputs**

- `comments` (list): The comments, newest first.
- `count` (number): How many are listed here.
- `page` (number): The page returned, 1 first.
- `per_page` (number): The page size asked for.
- `summary` (text): One line describing the result.
- `total` (number): How many match in all, across every page, when the API says.

**Example output**

```json
{
  "comments": [
    {
      "author": "Alexandre Dulaunoy",
      "created": "2026-10-04T10:25:17.263988+00:00",
      "description": "A memory overflow vulnerability in Citrix NetScaler ADC.",
      "tags": [
        "vulnerability:information=annotation"
      ],
      "title": "Understanding and Addressing CVE-2026-88779",
      "url": "https://vulnerability.circl.lu/comment/007803cc-3d1a-4c10-8b21-0de3fcce8425",
      "uuid": "007803cc-3d1a-4c10-8b21-0de3fcce8425",
      "vulnerability_id": "CVE-2026-88779"
    }
  ],
  "count": 1,
  "page": 1,
  "per_page": 20,
  "summary": "122 comments",
  "total": 122
}
```

### List detection rules

List ready-made detection rules (Sigma, YARA, Suricata, Sagan and others) from Rulezet that spot attempts to exploit a vulnerability, with each rule's text.

**Inputs**

- Vulnerability ID (`vulnerability_id`, text, required): A vulnerability id such as CVE-2021-44228, GHSA-jfh8-c2jp-5v3q or PYSEC-2021-19. A vulnerability page's address works too.
- Page (`page`, number): Which page to return, 1 first. From 1 to 100000.
- Per page (`per_page`, number): How many to return, 1 to 100. Defaults to 10. From 1 to 100.

**Outputs**

- `count` (number): How many are listed here.
- `page` (number): The page returned, 1 first.
- `per_page` (number): The page size asked for.
- `rules` (list): The rules.
- `summary` (text): One line describing the result.
- `total` (number): How many match in all, across every page, when the API says.
- `vulnerability_id` (text): The vulnerability.

**Example output**

```json
{
  "count": 1,
  "page": 1,
  "per_page": 20,
  "rules": [
    {
      "created": "2026-09-16 12:33",
      "format": "sagan",
      "rule": "alert any $EXTERNAL_NET any -> $HOME_NET any (msg: \"Log4j\"; content:\"jndi\";)",
      "title": "[APACHE] Log4j exploit attempt via hex encoding - CVE-2021-44228",
      "updated": "2026-09-16 12:33",
      "url": "https://rulezet.org/rule/detail_rule/750192"
    }
  ],
  "summary": "CVE-2021-44228: 158 detection rules (sagan on this page)",
  "total": 158,
  "vulnerability_id": "CVE-2021-44228"
}
```

### List known-exploited vulnerabilities

List entries in the known-exploited (KEV) catalogs Vulnerability-Lookup gathers, such as everything listed this week, with the catalog, its confidence and its notes.

**Inputs**

- From (`date_from`, date): Only those on or after this day.
- To (`date_to`, date): Only those on or before this day.
- Status (`status_reason`, text): Only entries with this status. Leave empty for any. One of: `confirmed`, `suspected`, `disputed`, `historical`, `unknown`, `withdrawn`.
- Page (`page`, number): Which page to return, 1 first. From 1 to 100000.
- Per page (`per_page`, number): How many to return, 1 to 1000. Defaults to 100. From 1 to 1000.

**Outputs**

- `count` (number): How many are listed here.
- `entries` (list): The catalog entries, newest first.
- `page` (number): The page returned, 1 first.
- `per_page` (number): The page size asked for.
- `summary` (text): One line describing the result.
- `total` (number): How many match in all, across every page, when the API says.

**Example output**

```json
{
  "count": 1,
  "entries": [
    {
      "catalog": "cisa-kev",
      "catalog_name": "CISA Known Exploited Vulnerabilities Catalog",
      "exploited": true,
      "first_seen": "2021-12-10T00:00:00+00:00",
      "last_seen": null,
      "notes": "KEV entry: Apache Log4j2 Remote Code Execution Vulnerability | Due date: 2021-12-24",
      "status_reason": "confirmed",
      "status_updated": "2021-12-10T00:00:00+00:00",
      "vulnerability_id": "CVE-2021-44228"
    }
  ],
  "page": 1,
  "per_page": 100,
  "summary": "98 known-exploited entries since 2026-10-01",
  "total": 98
}
```

### List most sighted vulnerabilities

Rank the vulnerabilities with the most sightings, a measure of what attackers and researchers are talking about, optionally for a date range or one kind of sighting such as exploited.

**Inputs**

- From (`date_from`, date): Only those on or after this day.
- To (`date_to`, date): Only those on or before this day.
- Sighting type (`sighting_type`, text): Only sightings of this kind. Leave empty for every kind. One of: `seen` (Seen (mentioned or discussed)), `exploited`, `published-proof-of-concept` (Proof of concept published), `confirmed`, `patched`, `not-exploited` (Not exploited), `not-confirmed` (Not confirmed), `not-patched` (Not patched).
- How many (`limit`, number): How many to rank, 1 to 100. Defaults to 10. From 1 to 100.

**Outputs**

- `count` (number): How many are listed here.
- `summary` (text): One line describing the result.
- `vulnerabilities` (list): The vulnerabilities, most sighted first.

**Example output**

```json
{
  "count": 1,
  "summary": "1 vulnerability, led by CVE-2025-55182 (1,968 sightings)",
  "vulnerabilities": [
    {
      "rank": 1,
      "sightings": 1968,
      "vulnerability_id": "CVE-2025-55182"
    }
  ]
}
```

### List product vulnerabilities

List the vulnerabilities affecting one vendor's product, such as apache log4j, newest first, optionally only those published or changed since a day.

**Inputs**

- Vendor (`vendor`, text, required): The vendor as Vulnerability-Lookup names it, such as apache or microsoft. Use 'List vendors' to find one.
- Product (`product`, text, required): The product. Pick one once the vendor is set, or type it, e.g. log4j.
- Changed since (`since`, date): Only those changed on or after this day. Leave empty for any time.
- Page (`page`, number): Which page to return, 1 first. From 1 to 100000.
- Per page (`per_page`, number): How many to return, 1 to 100. Defaults to 10. From 1 to 100.

**Outputs**

- `count` (number): How many are listed here.
- `page` (number): The page returned, 1 first.
- `per_page` (number): The page size asked for.
- `product` (text): The product.
- `since` (text): The day the list starts from, when one was given.
- `summary` (text): One line describing the result.
- `total` (number): How many match in all, across every page, when the API says.
- `vendor` (text): The vendor.
- `vulnerabilities` (list): The vulnerabilities.

**Example output**

```json
{
  "count": 1,
  "page": 1,
  "per_page": 10,
  "product": "log4j",
  "since": null,
  "summary": "apache log4j: 40 vulnerabilities",
  "total": 40,
  "vendor": "apache",
  "vulnerabilities": [
    {
      "aliases": [],
      "cvss_score": 10.0,
      "cvss_version": "3.1",
      "cwes": [
        "CWE-502",
        "CWE-400",
        "CWE-20"
      ],
      "description": "Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints.",
      "format": "cve",
      "id": "CVE-2021-44228",
      "published": "2021-12-10T00:00:00.000Z",
      "severity": "critical",
      "source": "cvelistv5",
      "summary": "CVE-2021-44228 (critical, CVSS 10.0): Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints",
      "title": "Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints",
      "updated": "2025-10-21T23:25:23.121Z",
      "url": "https://vulnerability.circl.lu/vuln/CVE-2021-44228"
    }
  ]
}
```

### List recent vulnerabilities

List the newest vulnerabilities from one source: new CVEs by default, or GitHub advisories, PyPI, a vendor's advisories (such as csaf_cisco or csaf_redhat) and dozens more. Optionally only those changed since a day or tied to one weakness (CWE).

**Inputs**

- Source (`source`, text): Where to read from. Leave empty for the CVE list (cvelistv5).
- Changed since (`since`, date): Only those changed on or after this day. Leave empty for any time.
- Order (`sort_by`, text): Newest published first, or most recently updated first. One of: `published` (Newest published first (default)), `updated` (Most recently updated first).
- Weakness (CWE) (`cwe`, text): Only those caused by this weakness, e.g. CWE-79 or 79.
- How many (`limit`, number): How many to return, 1 to 100. Defaults to 10. From 1 to 100.

**Outputs**

- `count` (number): How many are listed here.
- `since` (text): The day the list starts from, when one was given.
- `sort_by` (text): published or updated.
- `source` (text): The source read.
- `summary` (text): One line describing the result.
- `vulnerabilities` (list): The vulnerabilities.

**Example output**

```json
{
  "count": 1,
  "since": null,
  "sort_by": "published",
  "source": "cvelistv5",
  "summary": "1 vulnerability from cvelistv5, newest CVE-2021-44228",
  "vulnerabilities": [
    {
      "aliases": [],
      "cvss_score": 10.0,
      "cvss_version": "3.1",
      "cwes": [
        "CWE-502",
        "CWE-400",
        "CWE-20"
      ],
      "description": "Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints.",
      "format": "cve",
      "id": "CVE-2021-44228",
      "published": "2021-12-10T00:00:00.000Z",
      "severity": "critical",
      "source": "cvelistv5",
      "summary": "CVE-2021-44228 (critical, CVSS 10.0): Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints",
      "title": "Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints",
      "updated": "2025-10-21T23:25:23.121Z",
      "url": "https://vulnerability.circl.lu/vuln/CVE-2021-44228"
    }
  ]
}
```

### List sightings

List sightings: reports that a vulnerability was seen discussed, exploited, given a public proof of concept or patched, with where it was seen. Filter by vulnerability, kind and dates.

**Inputs**

- Vulnerability ID (`vulnerability_id`, text): Only those about this vulnerability, e.g. CVE-2021-44228. Leave empty for all.
- Sighting type (`sighting_type`, text): Only sightings of this kind. Leave empty for every kind. One of: `seen` (Seen (mentioned or discussed)), `exploited`, `published-proof-of-concept` (Proof of concept published), `confirmed`, `patched`, `not-exploited` (Not exploited), `not-confirmed` (Not confirmed), `not-patched` (Not patched).
- From (`date_from`, date): Only those on or after this day.
- To (`date_to`, date): Only those on or before this day.
- Page (`page`, number): Which page to return, 1 first. From 1 to 100000.
- Per page (`per_page`, number): How many to return, 1 to 1000. Defaults to 20 (100 for sightings). From 1 to 1000.

**Outputs**

- `count` (number): How many are listed here.
- `page` (number): The page returned, 1 first.
- `per_page` (number): The page size asked for.
- `sightings` (list): The sightings, newest first.
- `summary` (text): One line describing the result.
- `total` (number): How many match in all, across every page, when the API says.

**Example output**

```json
{
  "count": 1,
  "page": 1,
  "per_page": 100,
  "sightings": [
    {
      "author": "automation",
      "created": "2026-10-19T05:40:01+00:00",
      "source": "https://gist.github.com/jokerking-oss/3fb0aa09448471e319a499d553f200fe",
      "type": "seen",
      "uuid": "b6f24c81-dbe9-45e2-ab35-fc92d19862ac",
      "vulnerability_id": "CVE-2021-44228"
    }
  ],
  "summary": "1,964 sightings of CVE-2021-44228",
  "total": 1964
}
```

### List top vendors

Rank the vendors with the most vulnerabilities published, for all time, a year or one month.

**Inputs**

- Year (`year`, number): Only this year, e.g. 2026. Leave empty for all time. From 1999 to 2100.
- Month (`month`, text): Only this month of the year. Leave empty for the whole year. One of: `1` (January), `2` (February), `3` (March), `4` (April), `5` (May), `6` (June), `7` (July), `8` (August), `9` (September), `10` (October), `11` (November), `12` (December).
- Source (`source`, text): Whose records to count. Defaults to the CVE list. One of: `cvelistv5` (CVE list (default)), `certfr_avis` (CERT-FR advisories), `certfr_alerte` (CERT-FR alerts), `euvd` (EU Vulnerability Database).
- How many (`limit`, number): How many to rank, 1 to 100. Defaults to 10. From 1 to 100.

**Outputs**

- `count` (number): How many are listed here.
- `period` (text): The year (YYYY) or month (YYYY-MM) counted, or empty for all time.
- `source` (text): The source counted.
- `summary` (text): One line describing the result.
- `vendors` (list): The vendors, most vulnerabilities first.

**Example output**

```json
{
  "count": 1,
  "period": "2026",
  "source": "cvelistv5",
  "summary": "1 vendor in 2026, led by linux (7,859)",
  "vendors": [
    {
      "rank": 1,
      "vendor": "linux",
      "vulnerabilities": 7859
    }
  ]
}
```

### List top weaknesses

Rank the weaknesses (CWEs) most often behind vulnerabilities, for all time, a year or one month.

**Inputs**

- Year (`year`, number): Only this year, e.g. 2026. Leave empty for all time. From 1999 to 2100.
- Month (`month`, text): Only this month of the year. Leave empty for the whole year. One of: `1` (January), `2` (February), `3` (March), `4` (April), `5` (May), `6` (June), `7` (July), `8` (August), `9` (September), `10` (October), `11` (November), `12` (December).
- How many (`limit`, number): How many to rank, 1 to 100. Defaults to 10. From 1 to 100.

**Outputs**

- `count` (number): How many are listed here.
- `cwes` (list): The weaknesses, most common first.
- `period` (text): The year (YYYY) or month (YYYY-MM) counted, or empty for all time.
- `summary` (text): One line describing the result.

**Example output**

```json
{
  "count": 1,
  "cwes": [
    {
      "cwe_id": "CWE-122",
      "rank": 1,
      "vulnerabilities": 10870
    }
  ],
  "period": "2026-09",
  "summary": "1 weakness in 2026-09, led by CWE-122 (10,870)"
}
```

### List vendor products

List a vendor's products that have known vulnerabilities, most recently changed first, optionally those whose name contains some text.

**Inputs**

- Vendor (`vendor`, text, required): The vendor as Vulnerability-Lookup names it, such as apache or microsoft. Use 'List vendors' to find one.
- Name contains (`search`, text): Only products whose name contains this, e.g. log4j.
- Changed since (`since`, date): Only those changed on or after this day. Leave empty for any time.
- Page (`page`, number): Which page to return, 1 first. From 1 to 100000.
- Per page (`per_page`, number): How many to return, 1 to 1000. Defaults to 100. From 1 to 1000.

**Outputs**

- `count` (number): How many are listed here.
- `page` (number): The page returned, 1 first.
- `per_page` (number): The page size asked for.
- `products` (list): The products, most recently changed first.
- `summary` (text): One line describing the result.
- `total` (number): How many match in all, across every page, when the API says.
- `vendor` (text): The vendor.

**Example output**

```json
{
  "count": 1,
  "page": 1,
  "per_page": 100,
  "products": [
    {
      "last_change": "2026-09-30T12:00:00+00:00",
      "name": "log4j"
    }
  ],
  "summary": "apache: 15 products matching 'log4j'",
  "total": 15,
  "vendor": "apache"
}
```

### List vendors

Find vendors with known vulnerabilities, most recently changed first, optionally those whose name contains some text. Use a name with 'List vendor products' or 'List product vulnerabilities'.

**Inputs**

- Name contains (`search`, text): Only vendors whose name contains this, e.g. apache.
- Changed since (`since`, date): Only those changed on or after this day. Leave empty for any time.
- Page (`page`, number): Which page to return, 1 first. From 1 to 100000.
- Per page (`per_page`, number): How many to return, 1 to 1000. Defaults to 100. From 1 to 1000.

**Outputs**

- `count` (number): How many are listed here.
- `page` (number): The page returned, 1 first.
- `per_page` (number): The page size asked for.
- `summary` (text): One line describing the result.
- `total` (number): How many match in all, across every page, when the API says.
- `vendors` (list): The vendors, most recently changed first.

**Example output**

```json
{
  "count": 1,
  "page": 1,
  "per_page": 100,
  "summary": "21 vendors matching 'apache'",
  "total": 21,
  "vendors": [
    {
      "last_change": "2026-10-18T21:10:00.120000+00:00",
      "name": "apache"
    }
  ]
}
```

### Search vulnerabilities

Search vulnerability descriptions for words, such as a product name or 'remote code execution jenkins'. Searches the CVE list unless other sources are chosen.

**Inputs**

- Search for (`query`, text, required): The words to look for.
- Sources (`sources`, list): Where to search. Leave empty for the CVE list. One or more of: `cvelistv5` (CVE list (default)), `fkie_nvd` (NVD (FKIE mirror)), `variot` (VARIoT (IoT)), `certfr_avis` (CERT-FR advisories), `certfr_alerte` (CERT-FR alerts).
- Page (`page`, number): Which page to return, 1 first. From 1 to 100000.
- Per page (`per_page`, number): How many to return, 1 to 100. Defaults to 10. From 1 to 100.

**Outputs**

- `count` (number): How many are listed here.
- `page` (number): The page returned, 1 first.
- `per_page` (number): The page size asked for.
- `query` (text): The words searched for.
- `summary` (text): One line describing the result.
- `total` (number): How many match in all, across every page, when the API says.
- `vulnerabilities` (list): The vulnerabilities.

**Example output**

```json
{
  "count": 1,
  "page": 1,
  "per_page": 10,
  "query": "log4j",
  "summary": "118 matches for 'log4j'",
  "total": 118,
  "vulnerabilities": [
    {
      "aliases": [],
      "cvss_score": 10.0,
      "cvss_version": "3.1",
      "cwes": [
        "CWE-502",
        "CWE-400",
        "CWE-20"
      ],
      "description": "Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints.",
      "format": "cve",
      "id": "CVE-2021-44228",
      "published": "2021-12-10T00:00:00.000Z",
      "severity": "critical",
      "source": null,
      "summary": "CVE-2021-44228 (critical, CVSS 10.0): Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints",
      "title": "Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints",
      "updated": "2025-10-21T23:25:23.121Z",
      "url": "https://vulnerability.circl.lu/vuln/CVE-2021-44228"
    }
  ]
}
```

### Search vulnerabilities by CPE

List the vulnerabilities for the vendor and product a CPE name identifies, such as cpe:2.3:a:apache:log4j. CPE is the standard naming scheme scanners and asset inventories use for software.

**Inputs**

- CPE (`cpe`, text, required): The CPE name, with at least a vendor and product.
- Source (`source`, text): Where to look. Defaults to the CVE list. One of: `cvelistv5` (CVE list (default)), `nvd`, `fkie_nvd` (NVD (FKIE mirror)).
- Page (`page`, number): Which page to return, 1 first. From 1 to 100000.
- Per page (`per_page`, number): How many to return, 1 to 100. Defaults to 10. From 1 to 100.

**Outputs**

- `count` (number): How many are listed here.
- `cpe` (text): The CPE searched for.
- `page` (number): The page returned, 1 first.
- `per_page` (number): The page size asked for.
- `source` (text): The source searched.
- `summary` (text): One line describing the result.
- `total` (number): How many match in all, across every page, when the API says.
- `vulnerabilities` (list): The vulnerabilities.

**Example output**

```json
{
  "count": 1,
  "cpe": "cpe:2.3:a:apache:log4j",
  "page": 1,
  "per_page": 10,
  "source": "cvelistv5",
  "summary": "1 vulnerability for cpe:2.3:a:apache:log4j",
  "total": null,
  "vulnerabilities": [
    {
      "aliases": [],
      "cvss_score": 10.0,
      "cvss_version": "3.1",
      "cwes": [
        "CWE-502",
        "CWE-400",
        "CWE-20"
      ],
      "description": "Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints.",
      "format": "cve",
      "id": "CVE-2021-44228",
      "published": "2021-12-10T00:00:00.000Z",
      "severity": "critical",
      "source": "cvelistv5",
      "summary": "CVE-2021-44228 (critical, CVSS 10.0): Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints",
      "title": "Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints",
      "updated": "2025-10-21T23:25:23.121Z",
      "url": "https://vulnerability.circl.lu/vuln/CVE-2021-44228"
    }
  ]
}
```
