The vulnerability management process begins with reliable information about which vulnerabilities exist. Over the past couple of years the ecosystem of vulnerability data sources has experienced a genuine earthquake. What once seemed permanent and unshakable — a single CVE database carefully enriched by the American NVD — has suddenly become unstable. This article examines where to obtain vulnerability data today and why depending on one source has become risky.
Primary Vulnerability Data Sources for the Russian Market
BDU FSTEC (bdu.fstec.ru) is the Russian national threat database. Its advantages include orientation toward the Russian market and legislation, official state-recognized data, detailed descriptions with remediation recommendations, and coverage of domestic software that may be absent from Western databases. As of August 2026 the database contains more than 92 thousand vulnerabilities. Entries use identifiers in the format BDU:2024-01398. Users can find descriptions, consequences, and mitigation guidance. FSTEC also maintains a separate section on the most dangerous trending vulnerabilities, serving as the Russian analogue of the catalog of exploited vulnerabilities.
NVD (nvd.nist.gov), maintained by NIST, is the American national vulnerability database. It offers broad coverage, detailed descriptions, and mappings to CVSS and CPE. However, NVD has been at the center of the main drama of recent years, which is discussed below.
The CVE database maintained by MITRE is the international registry of vulnerability identifiers. CVE serves as the global identification standard; the same identifier CVE-2021-44228 (Log4Shell) is recognized worldwide. Both NVD and BDU, as well as vendor products, rely on CVE records.
Vendor security bulletins from software manufacturers such as Microsoft, Cisco, Astra Group, Positive Technologies and others frequently provide the earliest and most accurate information.


