CVE Monitor — New Vulnerability Feed with Alerts
Pricing
from $1.00 / 1,000 results
CVE Monitor — New Vulnerability Feed with Alerts
Monitor the NIST National Vulnerability Database (NVD) for new and updated CVEs. Filter by vendor, product, CVSS score, or severity level. Get instant Telegram alerts when critical vulnerabilities affect your stack.
Pricing
from $1.00 / 1,000 results
Rating
0.0
(0)
Developer

Genoff Márk
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
🛡️ NVD CVE Monitor — New Vulnerability Feed with Alerts
Track new and updated CVEs from the NIST National Vulnerability Database. Get Telegram alerts when critical vulnerabilities affect your vendors or products.
No proxy needed. Uses the official NVD REST API v2. Free plan compatible. Optional free API key for higher rate limits.
🔍 What it does
This Actor monitors nvd.nist.gov — the authoritative US government database of all known software vulnerabilities. Every CVE published or updated anywhere in the world ends up here.
| Feature | Detail |
|---|---|
| Source | NIST NVD API v2 (official) |
| Coverage | All CVEs worldwide |
| Update frequency | Continuous (NVD updates throughout the day) |
| Proxy needed | ❌ No |
| API key needed | ❌ No (optional for higher rate limits) |
✅ Key features
- Keyword filter — monitor specific vendors or products (e.g.
Microsoft,Apache,Cisco) - CVSS score filter — only alert on CVEs above your threshold (e.g. >= 7.0)
- Severity filter — CRITICAL / HIGH / MEDIUM / LOW
- Delta mode — KV Store tracks seen CVE IDs; only new ones returned each run
- Modified CVE tracking — optionally alert when existing CVEs get updated scores
- Telegram alerts — 1 summary message per run, sorted by severity
- Webhook support — push to Zapier, Make, n8n, Slack, PagerDuty
- Rich output — CVSS v3 score + vector, affected vendors/products, CWE IDs, references
📦 Output fields
{"cve_id": "CVE-2025-12345","published": "2025-04-15T10:00:00.000","last_modified": "2025-04-15T12:00:00.000","vuln_status": "Analyzed","description": "A heap buffer overflow vulnerability in...","description_short": "A heap buffer overflow vulnerability in...","cvss_v3_score": 9.8,"cvss_v3_severity": "CRITICAL","cvss_v3_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","cvss_v2_score": 7.5,"severity": "CRITICAL","affected_vendors": ["microsoft", "apache"],"affected_products": [{ "vendor": "microsoft", "product": "windows_11", "version": "22h2" }],"cwe_ids": ["CWE-787"],"references": [{ "url": "https://...", "source": "...", "tags": ["Patch", "Vendor Advisory"] }],"nvd_url": "https://nvd.nist.gov/vuln/detail/CVE-2025-12345","scraped_at": "2025-04-15T12:00:00.000Z"}
🚀 Example configurations
Daily critical/high alert — all vendors
{"severities": ["CRITICAL", "HIGH"],"delta_mode": true,"days_back": 1,"telegram_bot_token": "@TELEGRAM_TOKEN","telegram_chat_id": "YOUR_CHAT_ID"}
Microsoft + Apache only — score >= 7.0
{"keywords": ["Microsoft", "Apache"],"min_cvss_score": 7.0,"delta_mode": true,"days_back": 1}
Weekly digest — all severities
{"delta_mode": true,"days_back": 7,"max_cves": 500,"include_modified": true}
Historical pull — last 30 days, critical only
{"severities": ["CRITICAL"],"delta_mode": false,"days_back": 30,"max_cves": 2000}
📱 Telegram setup (4 steps)
Step 1 — Open Telegram → search @BotFather → /newbot → copy your token.
Step 2 — Get your Chat ID from @userinfobot.
Step 3 — In Apify Console → Settings → Secrets → add TELEGRAM_TOKEN.
Step 4 — Add to input:
{"telegram_bot_token": "@TELEGRAM_TOKEN","telegram_chat_id": "YOUR_CHAT_ID"}
Example alert:
🛡 NVD CVE AlertApr 15, 2025 — 4 new vulnerabilities🔴 CRITICAL: 1 🟠 HIGH: 3🔴 CVE-2025-12345 | CVSS 9.8 — CRITICAL📦 microsoft, windowsA heap buffer overflow in Windows Print Spooler...🔗 CVE-2025-12345🟠 CVE-2025-12346 | CVSS 7.5 — HIGH📦 apache...
🔑 NVD API key (optional but recommended)
Without key: 5 requests / 30 seconds (sufficient for daily runs). With free key: 50 requests / 30 seconds (needed for large historical pulls).
Get a free key: nvd.nist.gov/developers/request-an-api-key
Store it as an Apify Secret and reference it as @NVD_API_KEY in the input.
📅 Recommended schedule
| Use case | Frequency |
|---|---|
| Critical/High CVE alerts | Every 6–12 hours |
| Full daily digest | Daily at 08:00 |
| Weekly security report | Weekly |
⚡ Pricing
Pay-per-result. Typical daily run (1 day, all severities): 20–150 new CVEs.
| Volume | Est. cost |
|---|---|
| 50 CVEs | ~$0.03 |
| 500 CVEs | ~$0.25 |
| 2,000 CVEs | ~$1.00 |
🛡️ Legal
All data is from the public NIST NVD API. No authentication bypassed. Rate limits respected per NVD fair-use policy.
🐛 Issues & roadmap
- CISA KEV integration (flag if CVE is actively exploited)
- EPSS score filter (exploit prediction scoring)
- CPE-based filtering (exact product version matching)
- Slack / Teams webhook templates