Out of 48,000 Vulnerabilities Only 1% Are Dangerous: How to Find Them Using CVSS 4.0, EPSS, KEV and FSTEC Methodology
The article is part 10 of the “Vulnerability Management for Beginners” series and focuses on the core challenge of prioritization: out of 48,185 vulnerabilities published in 2025, only about one percent showed signs of real-world exploitation.
Verizon DBIR 2026 reports that exploitation of vulnerabilities overtook stolen credentials as the leading initial access method at 31 percent. Effective prioritization requires complete asset inventory and categorization of every node in the infrastructure.
CVSS alone is insufficient because it measures technical severity rather than actual risk in a specific environment. In 2025 roughly 39 percent of vulnerabilities received high or critical scores, yet the vast majority are never exploited. Additional factors include possible consequences of exploitation, asset criticality, presence of public exploits, attacker accessibility, and trending actively exploited vulnerabilities.
CVSS 4.0, released by FIRST in November 2023, introduced explicit nomenclature such as CVSS-B, CVSS-BT, CVSS-BE and CVSS-BTE, the new Attack Requirements metric, more granular User Interaction values, and a dual impact model separating vulnerable and subsequent systems. However, only 25.9 percent of 2025 vulnerabilities received CVSS 4.0 scores because major sources like NVD still rarely publish them.
In April 2026 NIST announced that NVD would enrich only vulnerabilities in the actively exploited catalog, federal U.S. software, or critical software lists. Approximately 29,000 accumulated records were moved to “not planned for processing,” forcing organizations to rely on vendor scores or calculate their own.
EPSS answers whether a vulnerability will be exploited within the next 30 days using machine learning. Version 4 released in March 2025 added malware telemetry and now observes activity across roughly 12,000 vulnerabilities monthly. A threshold of EPSS greater than 0.1 achieves 63.2 percent coverage with 65.2 percent precision, dramatically better than the common CVSS 7+ approach.
CISA KEV contains vulnerabilities with confirmed exploitation in real attacks. By July 2026 the catalog reached approximately 1,650 entries. The new BOD 26-04 directive introduced risk-based timelines, with the hottest issues required to be remediated within three days. Commercial alternatives such as VulnCheck KEV contain over 3,600 records and detect exploitation on average 27 days earlier.
The article also introduces the experimental LEV metric from NIST CSWP 41 that aggregates historical EPSS scores to highlight older vulnerabilities that were likely exploited but never catalogued. Both EPSS and KEV depend on CVE identifiers, creating limitations for Russian infrastructure where many vulnerabilities lack CVE entries and must be assessed using FSTEC BDU data instead.
Related articles
Nightmare Eclipse Publishes SignDrop Zero-Day in Windows CLFS Driver
Security researcher Abdelhamid Naseri, known as Nightmare Eclipse, has disclosed a new zero-day vulnerability named SignDrop affecting the Common Log File System (CLFS) driver in Windows. The flaw allows attackers to bypass authentication protections introduced by Microsoft in October 2025 and escalate privileges on affected systems. SignDrop exploits the way CLFS handles .cnpf authentication file creation when a new log file is generated, enabling a privileged process to open the file later and create it with SYSTEM rights. The technique can also be abused against any antivirus or EDR engine to disable self-protection mechanisms by making file creation requests appear to originate from the legitimate security process itself. Nightmare Eclipse confirmed the issue works on Windows 11 26H2, Windows 11 26H2 Experimental, and Windows Server 2025 Experimental, impacting an estimated 80 percent of Windows installations. No workaround exists other than waiting for a Microsoft patch, as disabling CLFS protections would reintroduce memory corruption risks. The researcher previously released multiple other zero-days, including BigDiskBuster and RoguePlanet targeting Microsoft Defender.
Telegram Patches RCE Vulnerabilities in HTML Widgets After Researcher Demonstrates Calculator Exploit
Telegram introduced HTML widgets for bots in early November, allowing JavaScript execution inside messages via the QuickJS engine. Security researcher V12 quickly demonstrated remote code execution by launching the system calculator on Android. Pavel Durov responded that no vulnerability existed because the user had to first start the bot, yet server-side fixes were deployed anyway. Multiple use-after-free and use-after-return bugs were identified in QuickJS and QuickJS-ng, some discovered with AI assistance from Claude Fable 5.1 and Mythos 5.2. Telegram isolated the widget engine into a separate process on Android, added syscall filtering, and limited nested graphical effects to prevent crashes. Desktop clients received the fixes across versions 7.4.2 and 7.4.3, while widgets were temporarily restricted server-side. Users are advised to update to Android 13.2.2 or Desktop 7.4.3 and avoid unknown bots.
Telegram Patches Critical QuickJS Sandbox Escape Vulnerability in Android Update 13.2.2
Telegram has released version 13.2.2 for Android to address a high-severity vulnerability in its HTML widgets for bots. The flaw resided in the QuickJS JavaScript engine within Telegram's QuickJS-ng fork and allowed scripts in ordinary messages to break out of the sandbox and execute native code on the device. The root cause was improper handling of the await using construct inside non-async functions, which triggered a use-after-return condition by freeing local variable references while nested functions still accessed the stack. The vulnerable code entered the QuickJS-ng main branch on May 16 as part of explicit resource management support. Security researcher Andreas Rösler discovered the issue during an AI-assisted audit with Anthropic's Claude model that identified 27 findings total. The patch enforces a syntax error on the invalid construct and was merged on November 10, the same day the Android release became available. Although reported against Android 13.2.1, the bug affected every platform using the affected engine fork.
Node.js Patches 16 Vulnerabilities Exposing TLS Private Keys and Cross-Connection Data
The Node.js project has released fixes addressing 16 vulnerabilities, seven of which are rated high severity. The most critical issue, CVE-2026-123864, allows an unauthenticated client to read memory from other HTTPS connections, potentially exposing TLS private keys and requests belonging to other users. Three supported release lines were affected, and exploitation requires a specific application code pattern involving res.flushHeaders() and res.end() calls before the request body is fully received. Additional high-severity flaws include CVE-2026-123863, which crashes HTTP/2 servers, CVE-2026-123866 that leaks server memory chunks to clients, and CVE-2026-123865 that causes permanent memory and file descriptor leaks in HTTP/2 servers. Several other CVEs affect TLS renegotiation, SNI callbacks, and file streaming functions. The project states that end-of-life branches including 20.x and 25.x remain vulnerable with no patches available.