vulnmatter-cli

n8n community node for CIRCL Vulnerability-Lookup API (https://vulnerability.circl.lu/api). API scope summary: vulnerabilities (by id, latest/recent, search by vendor/product and CPE), browse vendors/products, statistics (most commented/viewed vulnerabili

Package Information

Released: 9/11/2025
Downloads: 26 weekly / 53 monthly
Latest Version: 2.0.5
Author: VulnMatter Support

Documentation

n8n-nodes-vulnmatter-cli

n8n node to query the VulnMatter API and prioritize CVE vulnerabilities using advanced risk analysis algorithms.

Operation Description

This node allows:

  • CVE Prioritization: Analyzes a list of CVEs and returns a priority score based on multiple risk factors
  • Batch Processing: Handles multiple CVEs simultaneously to optimize performance
  • Advanced Analysis: Uses threat intelligence data, known exploits, and CVSS metrics to calculate priorities

Endpoint used

  • GET /v1/prioritizer/cves?ids=CVE-...,CVE-...
  • Header: X-API-Key: <your-key>

Requirements

⚠️ Registration required: To use this node you need:

  1. Register at https://vulnmatter.com/
  2. Generate an API Token from your user panel
  3. Configure credentials in n8n with your token

Installation

UI (n8n Cloud / self-hosted)

Settings → Community NodesInstall → search for n8n-nodes-vulnmatter-cli.

Docker (preinstalled)

environment:
  - N8N_COMMUNITY_PACKAGES=["n8n-nodes-vulnmatter-cli"]

Configuration

  1. Add credentials: In n8n, create new credentials of type "VulnMatter API"
  2. Base URL: https://api.vulnmatter.com (default)
  3. API Key: Your token generated from vulnmatter.com

Usage

Input modes

  • Manual list: Enter CVEs separated by commas (e.g: CVE-2024-1234,CVE-2024-5678)
  • From input items: Extract CVEs from workflow input data

Settings

  • Batch size: Number of CVEs to process per request (maximum 100)
  • CVE field: Name of the field containing the CVE when using input items

Response

The node returns for each CVE:

  • Priority score (0-100)
  • Severity level (Critical, High, Medium, Low)
  • Risk factors identified
  • Mitigation recommendations
  • Additional metadata from threat intelligence

Discussion