NVD Disruptions Force Security Teams to Diversify Vulnerability Intelligence Sources
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.
Related articles
From HFT to Infosec: How AI Accelerates the Developer-Hacker Arms Race
An experienced security researcher draws a parallel between high-frequency trading evolution and modern vulnerability research, showing how artificial intelligence compresses the time between patch release and working exploit. The author describes the classic workflow where developer Rob fixes buffer overflows in an FTP server while researcher Dave reverse-engineers the diff to locate the exact change. With AI assistance, both sides now generate patches or exploits in minutes rather than days or weeks. The piece highlights that publishing a patch effectively discloses the location of the flaw, allowing automated tools to produce reliable exploits almost instantly. Historical examples such as wu-ftpd CVEs and the EternalBlue/MS17-010 worm illustrate how quickly mass exploitation follows disclosure. The author warns that open-source projects face an existential dilemma: withhold patches and leave users exposed, or release them and trigger immediate automated scanning. Recommendations include mandatory back-porting of fixes and wider use of runtime protections, yet the overall outlook remains pessimistic about the coming wave of fully automated attacks.
Ghost Assets in Vulnerability Management: How Identification, Merging and Asset History Eliminate Anomalies in MaxPatrol VM
Positive Technologies experts explain how infrastructure changes create duplicate, merged and phantom assets that distort vulnerability management. The article details three core mechanisms inside MaxPatrol VM: unique asset identification across scan sources, non-destructive merging of new and existing data, and full lifecycle history with configurable aging policies. It describes how the system distinguishes assets using prioritized keys such as system ID, FQDN, MAC address and VM ID, then applies recursive merging rules that respect multiple data sources. Policies allow teams to set freshness and obsolescence thresholds, automatically hiding assets after 90 days while preserving historical snapshots for PDQL queries. The piece also covers practical cloning and partial-scan scenarios that can produce misleading duplicates or lingering collections.
GreyNoise Detects Active Exploitation Attempts of CVE-2021-36260 Against Hikvision Cameras
GreyNoise recorded exploitation attempts targeting CVE-2021-36260 in Hikvision cameras and recorders between September 21 and October 1. The vulnerability carries a CVSS score of 9.8 and allows unauthenticated remote command execution through insufficient input validation in the embedded web server. Attack traffic originated from four IP addresses, three routed through a commercial VPN in Lithuania and one from a Ukrainian residential network, with all targets located in Ukraine. Attackers leveraged a publicly available Nuclei template to probe devices, though GreyNoise confirmed only scanning activity and not successful compromises. The five-year-old flaw remains actively scanned despite an available firmware patch from Hikvision and a CISA advisory recommending immediate updates. Password changes provide no protection because the attack requires no authentication. Defenders are advised to apply firmware updates, remove devices from public internet exposure, and segment video surveillance networks from critical infrastructure.
Splunk Enterprise Discloses 46 Vulnerabilities Including Critical Patroni Authentication Flaw
Splunk has published three security advisories detailing a total of 46 vulnerabilities affecting Splunk Enterprise and related components. Three of the issues were rated critical, with CVE-2026-76268 receiving a CVSS v3.1 base score of 9.8. The flaw resides in the Patroni REST API used for PostgreSQL cluster management within search head clusters, allowing unauthenticated remote attackers to execute arbitrary operating system commands. Another high-severity issue, CVE-2026-76266, enables local privilege escalation to root on Linux systems during package updates. The remaining vulnerabilities cover product code, internally identified problems, and third-party packages. Organizations are urged to apply the available patches promptly.