Pre-NVD detection means spotting attack activity against a technology before the vulnerability behind it is published in the NVD, the US National Vulnerability Database where CVEs are listed and scored. Instead of waiting for a CVE, a CVSS score, or a KEV entry, you watch what attackers are probing right now.
Why it matters
Most vulnerability tools start from the NVD: no CVE, no alert. Attackers don’t wait for it. They map products first (which servers run Exchange, F5 BIG-IP, or a given WordPress plugin), and some exploit flaws weeks before anyone writes about them. CrowdSec saw CVE-2025-2748 exploited on 28 February 2025, 24 days before it was published in the NVD.
How CrowdSec does it
The Live Exploit Tracker runs reconnaissance rules on signals from more than 300,000 active Security Engines. Each rule detects probing of a product family, not of one CVE. When a new vulnerability lands, you already know who was scanning for that product, and a firewall subscribed to the vendor has already blocked those IPs.
Pre-NVD vs zero-day
A zero-day is a flaw exploited before a fix exists. Pre-NVD is about timing of knowledge: activity seen before the vulnerability is public in the NVD, whether it’s a true zero-day or a flaw already known to its vendor.
Frequently asked questions
The NVD (National Vulnerability Database) is the US government’s public database of vulnerabilities, run by NIST. It lists CVEs and adds a severity score (CVSS) and technical details. Most vulnerability scanners and patch tools rely on it.
Watch for attackers probing the product instead of waiting for a CVE number. Reconnaissance rules detect scans that target a product family (for example, requests that only make sense against a specific appliance or plugin). Rising probing can signal a vulnerability that’s about to be exploited, or already is. The CrowdSec Live Exploit Tracker shows this activity and the IPs behind it, so you can block them before the CVE appears.
Because the NVD runs behind. This year it has received 91,025 new CVEs and analyzed 42,528 of them, and 59,423 CVEs sit in “deferred” status (NVD dashboard, 29 October 2026). Attackers don’t wait for it: CrowdSec saw CVE-2025-2748 exploited on 28 February 2025, 24 days before it was published in the NVD. For SAP NetWeaver, our reconnaissance rule was tracking probing about nine months before CVE-2025-31324 was published (24 April 2025).
No. Zero-day detection is about flaws with no fix yet. Pre-NVD detection is about seeing attack activity before a vulnerability is listed in the NVD, which also covers flaws the vendor already knows about and may have patched.
