HabrAugust 26, 2026🇷🇺Translated from Russian

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

HabrVulnerabilities & Exploits

Fuzzy Logic in Cybersecurity: Reducing Vulnerability Queue by 7.5 Times with CVSS, EPSS and FSTEC Comparison

An information security specialist has developed a fuzzy logic system that prioritizes vulnerabilities far more effectively than traditional scoring methods. The approach uses linguistic variables and membership functions to handle the inherent uncertainty in exploitability and impact assessments. By integrating EPSS probability data with CVSS impact scores and vulnerability age, the model reduces the actionable backlog by a factor of 7.5. The implementation relies on the Mamdani inference algorithm and trapezoidal membership functions to produce smooth, human-interpretable urgency ratings. Detailed coverage checks and rule-base validation ensure no gaps exist in the decision space. Real-world testing on CVE-2025-49113 in Roundcube Webmail demonstrated practical advantages over rigid threshold logic. The method is positioned as a practical enhancement rather than a replacement for existing standards.

AntiMalwareVulnerabilities & Exploits

VLC Media Player Hit by Two Memory Corruption Flaws Exploitable via Malicious PNG and Rogue RealRTSP Server

Two vulnerabilities have been discovered in the VLC media player that allow out-of-bounds memory access. The issues affect versions from 3.0.0 through 3.0.23. CVE-2026-56711, rated 8.6 on CVSS 4.0, stems from an integer overflow when calculating image buffer sizes in PNG files, enabling attackers to trigger writes beyond allocated memory simply by opening a crafted image or loading it from a playlist. CVE-2026-73324, scored 6.9, resides in the RealRTSP module and permits a malicious server to send an oversized response string that causes reads past the end of a buffer due to a missing null terminator. Both flaws are present in official VideoLAN builds, although some distributions may exclude the RealRTSP component. No special configuration or plugins are required to trigger the issues. Until patched releases appear, users are advised to avoid opening images or playlists from untrusted sources and to refrain from connecting to unknown RealRTSP streams.

AntiMalwareVulnerabilities & Exploits

September Windows 11 Security Update KB5124008 Breaks Always On VPN Certificate Authentication

The September security update KB5124008 for Windows 11 has introduced a regression that disables Always On VPN connections using certificate-based authentication. The issue affects devices running Windows 11 versions 24H2 and 25H2 that connect to Remote Routing and Access Service (RRAS) and Network Policy Server (NPS) instances on Windows Server 2019. VPN profiles deployed via Microsoft Intune are impacted, with the failure occurring during the certificate negotiation phase of the IPsec connection. Users confirm the problem is reproducible: the VPN works before the patch, stops after installation, and resumes after patch removal and reboot. Microsoft has not yet acknowledged the regression or released a fix, leaving administrators to pause deployment through WSUS or Intune and open support cases with client and NPS logs. A potential workaround involves switching profiles to EAP-TLS, though its reliability remains unconfirmed.

HabrVulnerabilities & Exploits

API Token Lifecycle: From Issuance to Revocation and Secure Management

The article provides a comprehensive examination of the full API token lifecycle in browser-based applications, emphasizing that signatures alone cannot prevent token theft. It details risks introduced at issuance, storage, transmission, and revocation stages, including improper OAuth grant types and long-lived tokens. Key recommendations include short-lived access tokens, atomic refresh token rotation, and the use of Authorization Code Flow with PKCE for public clients. Storage advice strongly discourages localStorage and sessionStorage in favor of HttpOnly cookies or a Backend-for-Frontend pattern that keeps real tokens on the server. The piece also covers CSRF protections, rate limiting on authorization endpoints, and the advantages of signed client assertions over static secrets. Overall, it stresses that token security depends on the entire lifecycle architecture rather than cryptographic strength alone.