Habr•September 12, 2026•🇷🇺Translated from Russian

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

An experienced security analyst has built a fuzzy logic model that cuts the vulnerability remediation queue by a factor of 7.5 while providing more nuanced prioritization than CVSS, EPSS or the Russian FSTEC methodology.

From Ancient Paradoxes to Modern Vulnerability Scoring

The work begins with the classic Sorites paradox: removing one grain of sand from a heap does not stop it being a heap, yet continued removal eventually destroys the concept. This illustrates that many real-world categories have blurred boundaries. The same problem appears in vulnerability management when analysts apply hard thresholds such as “if CVSS ≥ 9.0 then critical.”

CVSS (Common Vulnerability Scoring System) version 3.1 produces a score from 0 to 10 together with an attack vector string. While useful, the metric answers only “how bad could exploitation be” and “how difficult is exploitation,” not “how likely is exploitation in the next 30 days.” EPSS (Exploit Prediction Scoring System) supplies the missing probability but still yields a single crisp number that analysts must threshold manually.

Fuzzy Sets and Membership Functions

Lotfi Zadeh introduced fuzzy sets in 1965, allowing an element to belong to a set to a degree between 0 and 1. Membership is not probability: a liquid with membership 0.91 in the set of drinkable fluids is almost certainly potable, whereas a probability of 0.91 only states that 91 out of 100 similar samples would be safe.

The analyst implemented four common membership function shapes: triangular, trapezoidal, Gaussian and sigmoidal. For EPSS values, which cluster heavily near zero, a logarithmic transformation combined with trapezoidal functions proved most practical. The linguistic variable for EPSS contains five terms: negligible, low, medium, high and critical.

Rule Base Construction and Mamdani Inference

A complete rule base must satisfy coverage and consistency. With three inputs each having three terms, 27 rules are required; five inputs would demand 3125 rules, so the author cascaded multiple smaller inference blocks. Each rule follows the form “IF EPSS is high AND impact is complete THEN urgency is immediate.”

The Mamdani algorithm performs four steps: fuzzification of crisp inputs, evaluation of rule firing strength using the minimum t-norm, aggregation of clipped output membership functions, and defuzzification by centroid calculation. In one test case (CVE-2025-49113 in Roundcube Webmail), an EPSS of 0.30, impact of 5.9 and age of 244 days produced an urgency score of 94.4, placing the issue in the “immediate, 24-hour window” category.

Practical Results and Comparison

Side-by-side evaluation against raw CVSS thresholds, EPSS probability cut-offs and the FSTEC risk matrix showed a 7.5-fold reduction in the number of vulnerabilities requiring urgent attention. The fuzzy model also avoided the “hole” problem where certain input combinations receive no rule coverage. The author notes that the Mamdani method is especially suitable when results must be explained to auditors, while a Sugeno-style approach would offer faster numerical tuning.

The complete implementation, written from scratch in approximately 200 lines of Python without external fuzzy libraries, is intended both as a working tool and as an educational artifact demonstrating every stage of fuzzy inference applied to real vulnerability data.

Related articles

Security NEXT•Vulnerabilities & Exploits

PHP Foundation Reveals Two Critical RCE Vulnerabilities Fixed After 2024 Discovery Delays

The PHP Foundation has disclosed details surrounding two severe remote code execution vulnerabilities in PHP that were addressed in updates released on October 21, 2026. The issues, tracked as CVE-2026-109618 and CVE-2026-109619, affect memory management and error handling routines used in nearly every request. Although signs of one flaw were identified during an external audit in 2024, resource constraints and prioritization of other issues delayed remediation. The foundation had planned a coordinated disclosure, but information leaked prematurely, causing confusion among stakeholders. Updated versions PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35 are now available, and immediate patching is strongly recommended for all users. The vulnerabilities' broad impact and the challenges in balancing security fixes with performance considerations made the response particularly complex.

Security NEXT•Vulnerabilities & Exploits

CISA Urges Immediate Patching of Critical PHP Remote Code Execution Vulnerabilities

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has issued an urgent advisory regarding two severe vulnerabilities in the PHP programming language that allow unauthenticated remote code execution. Identified as CVE-2026-109618 and CVE-2026-109619, the flaws affect all environments processing web requests with PHP and have been nicknamed php2shell. CISA recommends applying patches to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35 without delay, or taking affected systems offline if updates cannot be applied immediately. Although no exploitation has been observed yet, organizations are instructed to inventory PHP usage, prioritize internet-facing systems, and monitor for suspicious activity such as shell processes spawned from PHP workers. Web application firewalls may offer partial protection but are not considered a substitute for patching.

Security NEXT•Vulnerabilities & Exploits

GitLab Issues Critical Patches for CVE-2026-110264 Affecting Wide Range of Versions

GitLab has released emergency security updates to address multiple vulnerabilities, including one rated critical that allows unauthenticated remote code execution. The flaw, tracked as CVE-2026-110264, stems from an integer overflow in the regular expression compiler and carries a maximum CVSSv3.1 base score of 10.0. It impacts GitLab Community Edition and Enterprise Edition starting from version 7.0, with patches now available for both current and older branches. The company strongly urges immediate updates due to the severity and potential for arbitrary code execution on affected servers. Additional lower-severity issues were also resolved in the same release cycle.

Hispasec•Vulnerabilities & Exploits

PHP Issues Emergency Patches for Critical PHP2Shell RCE Flaws as Exploit Attempts Emerge

PHP has released urgent patches for two critical vulnerabilities collectively known as PHP2Shell that enable unauthenticated remote code execution on affected servers. The flaws, tracked as CVE-2026-109618 and CVE-2026-109619, score 9.2 on CVSS v4.0 and have already seen active exploitation attempts with malicious payloads adjusted to bypass WAF rules. The issues affect multiple PHP deployment methods including Apache with mod_php, PHP-FPM, php-cgi, FrankenPHP, and LiteSpeed, and do not require complex application code to be exploitable. CVE-2026-109618 involves a memory corruption chain leading to code execution under the web process privileges, while CVE-2026-109619 stems from an obsolete global state issue causing use-after-free conditions that can result in memory disclosure and code execution. Patched versions include PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35, with administrators advised to restart all persistent workers after updating. Temporary mitigations such as setting memory_limit to -1 and disabling session.upload_progress.enabled are available for environments that cannot patch immediately.