# Guides to ranking by exploitation, with the arithmetic shown

GUIDES, read 10 Nov 2026

**The short answer.** Eight guides: prioritizing by exploitation, reading a CVSS vector, using EPSS without fooling yourself, meeting KEV due dates under BOD 26-04, writing an SSVC tree, explaining a ranking to an auditor, why CVSS alone misranks, and building a weighted score from real ledger CVEs.

- [How to prioritize vulnerabilities by exploitation](/guides/prioritize-vulnerabilities-by-exploitation/): Exploitation evidence ranks a vulnerability better than severity does.
- [Reading a CVSS vector string, metric by metric](/guides/reading-a-cvss-vector-string/): Read the vector, not the number.
- [Using EPSS without fooling yourself](/guides/using-epss-without-fooling-yourself/): EPSS gives each CVE a probability of exploitation in the next 30 days, recalculated daily.
- [Meeting KEV due dates: BOD 22-01 and BOD 26-04](/guides/meeting-kev-due-dates-bod-22-01/): CISA's BOD 26-04, issued June 10, 2026, is the directive in force for KEV remediation.
- [Writing an SSVC decision tree for your organization](/guides/writing-an-ssvc-decision-tree/): SSVC replaces a score with a decision tree.
- [Explaining the ranking to an auditor](/guides/explaining-the-ranking-to-an-auditor/): An auditor wants to rerun your ranking, not admire it.
- [Why CVSS alone misranks exploited vulnerabilities](/guides/why-cvss-alone-misranks/): CVSS describes how severe a flaw is, not whether anyone is exploiting it.
- [Building a weighted priority score from CVSS, EPSS and KEV](/guides/building-a-weighted-priority-score/): A weighted score is arithmetic you can show.

Last reviewed 10 Nov 2026. Canonical: https://epssvscvss.com/guides/
