WORKED EXAMPLE, read 10 Nov 2026
A weighted score of 30 points for CVSS, 40 for EPSS and 30 for KEV ranks real CVEs sensibly
The formula
Score = 30 x (CVSS base / 10) + 40 x EPSS probability + 30 x KEV flag, where the KEV flag is 1 if the CVE is in the CISA catalog on the scoring date and 0 otherwise. The range is 0 to 100. These weights are an example chosen for clarity, not a standard from FIRST or CISA.
Each input has a source and a date. CVSS is the NVD base score (v3.1 for all five CVEs below). EPSS is the probability published for the KEV dateAdded, taken from the ledger. KEV status comes from the catalog entry.
Five CVEs from the ledger
The rows are from data/kev/ledger.json. All five are KEV entries, so the KEV term adds 30 to each and the ranking is decided by the other two terms. The ledger contains only listed entries, so it has no example of a CVE scoring 0 on the KEV term.
The ProFTPD and SmarterMail entries combine high CVSS with high EPSS and rank first. TeamCity ranks above Drupal even though its CVSS is lower, because its listing-day EPSS is 0.82. The VMware ESX entry sits last on every term.
| CVE | Product | KEV added | CVSS | EPSS that day | CVSS pts | EPSS pts | KEV pts | Score |
|---|---|---|---|---|---|---|---|---|
| CVE-2015-3306 | ProFTPD | 2026-10-08 | 10.0 | 0.96752 | 30.0 | 38.7 | 30 | 98.7 |
| CVE-2025-52691 | SmarterTools SmarterMail | 2026-01-26 | 10.0 | 0.73587 | 30.0 | 29.4 | 30 | 89.4 |
| CVE-2024-27199 | JetBrains TeamCity | 2026-04-20 | 7.3 | 0.82472 | 21.9 | 33.0 | 30 | 84.9 |
| CVE-2026-9082 | Drupal Core | 2026-05-22 | 9.8 | 0.00017 | 29.4 | 0.0 | 30 | 59.4 |
| CVE-2026-41709 | Broadcom VMware ESX | 2026-10-28 | 2.7 | 0.00297 | 8.1 | 0.1 | 30 | 38.2 |
Where it differs from CVSS alone
Ranked by CVSS, the order is ProFTPD and SmarterMail at 10.0, Drupal at 9.8, TeamCity at 7.3 and VMware ESX at 2.7. The weighted order swaps Drupal and TeamCity. TeamCity (CVE-2024-27199) carries the ledger's ransomware flag, and its EPSS says exploitation is likely, so the swap matches the evidence.
The weighted score does not fix the Drupal entry's EPSS of 0.00017. That value is tiny, and the entry was listed two days after NVD published it. The 30 KEV points hold it at 59.4. Without the KEV term it would have scored 29.4, below TeamCity's 54.9.
Add a floor and a gate
Two rules close the gaps. A floor: any KEV-listed CVE on an internet-facing asset goes to the top band regardless of score. A gate: a CVE that is not in KEV cannot score above 70 under these weights (30 + 40), so it cannot outrank a listed CVE on points alone, which suits a program that treats observed exploitation as decisive.
The VMware ESX entry shows the floor at work. At 38.2 it would be in the low band by score, yet CISA listed it on 2026-10-28 on evidence of exploitation. The floor lifts it to the top band and the log records why.
Weights and where platforms allow them
Choose the weights from the question you are answering and write them in the policy with the date. If you set EPSS at 40 points, an EPSS of 0.10 contributes 4 points. Check that the points your threshold implies match what you intend.
On the evidence read on 2026-11-10, the Signal Matrix shows customer weighting of the score documented for 5 of 13 profiled platforms. The cells for the others read none found on 2026-11-10. If your platform does not let you set weights, compute this score yourself from the exported fields and keep the formula under version control.
- Inputs per row: CVE, CVSS version and base score, EPSS probability and date, KEV flag and date.
- Output per row: points by term, total, band, and the rule that applied (score, floor or gate).
- Review weights every quarter and record the change.
Sensitivity of the weights
Change the weights and the order moves. With 50 points for CVSS, 20 for EPSS and 30 for KEV, TeamCity scores 36.5 + 16.5 + 30 = 83.0, and Drupal scores 49.0 + 0.0 + 30 = 79.0, so TeamCity still leads. With 70 for CVSS, 0 for EPSS and 30 for KEV, Drupal scores 98.6 against TeamCity's 81.1. The swap depends on giving EPSS real weight.
Run that check on any weights you adopt. Pick five CVEs where you already know the right order, score them, and confirm the formula agrees. A formula that disagrees with the cases you are sure about will disagree on the ones you are not.
Sources
- FIRST, EPSS frequently asked questions, read 10 Nov 2026
- FIRST, CVSS v3.1 Specification Document, read 10 Nov 2026
- CISA, BOD 26-04: Prioritizing Security Updates Based on Risk, read 10 Nov 2026
Last reviewed 10 Nov 2026.