An n8n workflow that uses the verified Apify node. NexGenData has no verified n8n node — you run a public-data Apify actor inside n8n through Apify’s verified node, on a schedule, with your own Apify token.
The problem: new vulnerabilities drop faster than teams can triage
Hundreds of CVEs publish weekly, but only a few matter to your stack — the ones affecting your vendors, especially anything on CISA’s Known Exploited Vulnerabilities (KEV) list or with a high EPSS score. Watching feeds by hand is noisy and slow. A scheduled n8n workflow filters to what’s relevant and alerts your team in Slack or an issue tracker the moment it lands.
Who this is for
Security, IT, and platform/dev teams who want vendor- and product-specific vulnerability alerts. (n8n self-hosts inside your own infra, which security teams often prefer.)
The n8n workflow
- Schedule Trigger — a few times a day.
- Apify node → Run Actor — CVE Vulnerability Monitor (NVD + CISA KEV + EPSS), with your vendors/products in the input.
- Get Dataset Items — CVE ID, CVSS, CISA KEV flag, EPSS, summary.
- Filter / Remove Duplicates — keep KEV = true OR CVSS ≥ 9; drop CVEs already seen.
- Send to destination — Slack alert, Gmail, Google Sheets, or HTTP Request into an issue tracker (free in n8n).
Sample input (vendor watchlist)
| vendor | product |
|---|---|
| fortinet | fortios |
| microsoft | windows |
| apache | struts |
Sample output (KEV-filtered alerts)
| cve_id | vendor | cvss | cisa_kev | epss | summary |
|---|---|---|---|---|---|
| CVE-2026-12345 | fortinet | 9.8 | true | 0.91 | Pre-auth RCE in SSL-VPN (exploited) |
| CVE-2026-30021 | apache | 9.1 | true | 0.77 | OGNL injection RCE |
Illustrative sample.
Run it on a schedule
Scheduled runs give your team a tuned vulnerability feed: only CVEs that hit your vendors and cross your severity/KEV threshold reach Slack — deduped, so no repeat noise.
Try it
Run the CVE Vulnerability Monitor →
Browse more: Cybersecurity & Domain Intelligence cluster
More n8n workflows
FAQ
What sources does it use? The actor combines NVD (CVE data), CISA KEV (known-exploited list), and EPSS (exploit-probability scoring).
How do I cut the noise? Filter on KEV = true or a CVSS/EPSS threshold and use Remove Duplicates keyed on CVE ID.
Is this a verified NexGenData n8n node? No — it’s an n8n workflow using Apify’s verified n8n node with your own Apify token.
⬇ Ready-made n8n template (CVE / CISA KEV → Slack)
Skip building it by hand — import this workflow straight into n8n:
- In n8n: Workflows → Import from URL and paste:
https://raw.githubusercontent.com/TheNextGenNexus/n8n-nodes-nexgendata/main/n8n-templates/n8n-cve-kev-to-slack.json - Open the HTTP Request node → set your Apify API token.
- Connect your destination (Sheets / Slack / Gmail), set the schedule, and activate.
Or download the template JSON → (built from core n8n nodes — nothing to install).