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
Google Releases Chrome 152 Fixing 327 Vulnerabilities Including 10 Critical Flaws
Google has released Chrome 152 for Windows, macOS, and Linux, addressing a total of 327 security vulnerabilities. Ten of these issues received the highest severity rating of Critical. The update resolves multiple Use After Free flaws in core components such as ANGLE, Aura, and Chromecast. Specific CVEs fixed include CVE-2026-79282 in ANGLE and several others in Aura and Chromecast modules. The release targets memory corruption and input validation weaknesses that could lead to remote code execution. Users are strongly advised to apply the update immediately to mitigate potential exploitation risks.
Veeam ONE Receives Security Update Addressing Critical Vulnerabilities Including CVE-2026-65641
Veeam Software has released updates for its backup environment monitoring tool Veeam ONE to address multiple vulnerabilities. The advisory covers the 13.x series and includes fixes rated as critical under CVSSv4.0. One flaw, CVE-2026-65641, allows service accounts to perform SMB authentication and carries a base score of 9.3. Additional high-severity issues such as CVE-2026-64633 with a perfect 10.0 score were also resolved in the patches. The company updated its disclosure to include seven vulnerabilities fixed in version 13.1.0.7034 after initially reporting six. Patches are now available for both the 13.x and 12.x branches, with the latest 12.3 Patch 1 backporting several fixes from the 13 series.
Three Critical Vulnerabilities in Adobe Campaign Classic Allow Arbitrary Code Execution
Adobe has disclosed three severe vulnerabilities in Adobe Campaign Classic that could permit attackers to execute arbitrary code on affected systems. The issues affect both Windows and Linux versions and include two OS command injection flaws along with one server-side request forgery vulnerability. Each vulnerability received the maximum CVSSv3.1 base score of 10.0 and is rated Critical. Adobe released fixes in version 7.4.4 build 9401, which must be applied to on-premises components in both pure on-premises and hybrid environments. Although no active exploitation has been observed, Adobe assigned the highest priority level and recommends applying the update within 72 hours.
Dirty COW CVE-2016-5195: How a 2016 Linux Kernel Race Condition Still Enables Privilege Escalation in Embedded Systems
The 2016 Linux kernel vulnerability CVE-2016-5195, known as Dirty COW, allowed local users to bypass copy-on-write protections and modify read-only memory mappings through a race condition involving writes to /proc/self/mem and madvise calls. Although patched in supported distributions years ago, the flaw persists in older kernels running on routers, cameras, and industrial controllers that receive infrequent firmware updates. Public exploits often target /etc/passwd or SUID binaries for root access, but success depends heavily on the presence of login mechanisms, BusyBox applets, and suitable binaries in the target environment. When standard targets are absent, attackers may pivot to overwriting vDSO functions in process memory to inject code executed by higher-privileged processes. The article explains why ready-made PoCs frequently fail on minimal BusyBox-based systems and outlines the checks required for architecture, ABI, vDSO symbols, and payload compatibility. It also references the practical exercise Strange And Dirty on the free White Hacker course for hands-on adaptation of the exploit chain.