Hermes Threat Score (HTS) Methodology & Divergence Engine
1. Why CVSS Fails as a Prioritization Strategy
Section titled β1. Why CVSS Fails as a Prioritization StrategyβEnterprise security teams face thousands of newly published vulnerabilities each month, the vast majority of which receive CVSS scores of 7.0 or higher. Treating CVSS as an operational patching queue leads to alert fatigue and critical blind spots:
- Theoretical vs. Realized Exploitability: A vulnerability with CVSS 9.8 may have zero functional exploits, require complex multi-step memory shaping, or affect an obsolete component deployed in less than 0.1% of networks.
- The βZero-to-Pawnedβ Velocity: A vulnerability rated CVSS 7.5 (High) that has been incorporated into automated ransomware exploit kits or CISAβs Known Exploited Vulnerabilities (KEV) catalog represents a catastrophic operational emergency.
HTS bridges the gap between static vulnerability descriptions and active threat operations by fusing:
- NVD / CWE Technical Metrics
- EPSS (Exploit Prediction Scoring System) probability distributions
- CISA KEV / In-the-Wild Exploitation Telemetry
- Public Exploit Maturity (PoC, Metasploit, Weaponized kits)
- Internet-Wide Exposure & Enterprise Product Prevalence
2. Dimensional Architecture (0β100 Scale)
Section titled β2. Dimensional Architecture (0β100 Scale)βThe Hermes Threat Score combines eight operational dimensions:
HTS TOTAL SCORE = Exploitability (20) + Threat Activity (20) + Weaponization (15) + Exposure (15) + Product Prevalence (10) + Impact (10) + Exploit Maturity (10)| Dimension | Weight | Criteria & Operational Evidence |
|---|---|---|
| Exploitability | 0β20 pts | Network accessibility, authentication barriers, and exploitation preconditions. |
| Threat Activity | 0β20 pts | Observed active exploitation in the wild, CISA KEV listing, honeypot telemetry hits. |
| Weaponization | 0β15 pts | Integration into public frameworks (Metasploit, Nuclei, Cobalt Strike) or dark web commercial loaders. |
| Exposure | 0β15 pts | Proportion of vulnerable instances exposed directly to the public internet (Shodan / Censys data). |
| Product Prevalence | 0β10 pts | Market share and enterprise ubiquity of the affected software or dependency. |
| Impact Severity | 0β10 pts | Scope of damage (Host RCE, unauthenticated data exfiltration, service denial). |
| Exploit Maturity | 0β10 pts | Reliability of the exploit (from theoretical PoC to 100% reliable automated weapon). |
3. Divergence Analysis: CVSS vs. Hermes
Section titled β3. Divergence Analysis: CVSS vs. HermesβOne of the most valuable capabilities of Hermes Codex is Divergence Analysis. Hermes automatically highlights situations where operational reality departs sharply from CVSS.
Case A: CVSS High / Hermes Low (The De-escalation Filter)
Section titled βCase A: CVSS High / Hermes Low (The De-escalation Filter)βCVSS: 9.8 (Critical) βββΊ HERMES THREAT SCORE: 34 (Low)- Why? The technical impact is devastating (RCE), but there is zero public exploit, exploitation requires non-default memory compiler flags, and the software is an obscure library with minimal internet exposure. Defenders can safely prioritize other active threats.
Case B: CVSS Moderate / Hermes Critical (The Escalation Alert)
Section titled βCase B: CVSS Moderate / Hermes Critical (The Escalation Alert)βCVSS: 6.8 (Medium) βββΊ HERMES THREAT SCORE: 92 (Critical)- Why? Although CVSS marks the vulnerability as medium because it only allows local information disclosure, active ransomware syndicates are chaining it with ubiquitous domain controllers to achieve full Active Directory compromise.
4. Live Benchmark Example: Roundcube CVE-2026-59822
Section titled β4. Live Benchmark Example: Roundcube CVE-2026-59822βBelow is an operational evaluation of CVE-2026-59822 (Roundcube Webmail Pre-Auth RCE):
HERMES THREAT SCORE
Target:Roundcube Webmail Core Server Full convergence between CVSS (9.8) and Hermes Threat Score (96). Active in-the-wild weaponization, CISA KEV catalog inclusion, public automated exploit kits, and widespread internet-facing webmail instances mandate immediate out-of-band patching.