Abstract
The Common Vulnerability Scoring System (CVSS) currently expresses severity on a scale whose maximum score is 10.0. In practice, this ceiling can leave insufficient numerical space to distinguish between vulnerabilities that are critical and vulnerabilities that are, informally speaking, really, really critical.
This document proposes CVSS-20, an extension of the scale to 20.0. It illustrates the temptation to address prioritisation noise by enlarging a score range rather than improving how scores are interpreted and used.
1. Status of This Memo
This document is an unofficial proposal. It is not an RFC, is not endorsed by FIRST or the CVSS Special Interest Group, and does not modify any version of CVSS. Distribution is unlimited, provided this notice is retained.
2. Conventions and Terminology
The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, and MAY in this document are to be interpreted as described in RFC 2119. Their use here creates no actual requirements.
3. Motivation
Operators have occasionally observed that several vulnerabilities receive the maximum severity score. This can make it difficult to identify which maximum-scored vulnerability should receive attention first.
Rather than improve prioritisation with additional context—such as exposure, exploitability in the relevant environment, available mitigations, and business impact—this proposal takes the direct route: add more numbers.
4. The Proposed Extension
A conforming CVSS-20 implementation would accept scores in the range 0.0 through 20.0, inclusive. Existing scores would be retained, with additional headroom reserved for increasingly emphatic descriptions.
0.0–3.9 Low 4.0–6.9 Medium 7.0–8.9 High 9.0–10.0 Critical 10.1–15.0 Really Critical 15.1–19.9 Extremely, Exceptionally Critical 20.0 Please Wake Up the CISO
Scores above 10.0 SHOULD be accompanied by at least one exclamation mark in executive summaries. A score of 20.0 MAY be accompanied by a red banner, an urgent calendar invitation, or both.
5. Backward Compatibility
Existing CVSS scores remain valid. A score of 10.0 retains its original meaning, except that it is no longer the maximum. Systems that cannot display scores greater than 10.0 MAY render them as “10.0+” and SHOULD look concerned.
6. Security Considerations
A larger score range does not, by itself, make vulnerability prioritisation more accurate. It may instead create a new upper-bound arms race, in which all sufficiently important vulnerabilities quickly converge on 20.0.
Readers are therefore reminded that severity scores are not a substitute for context-aware risk assessment or sound remediation decisions.
7. IANA Considerations
This document has no IANA actions.
8. Acknowledgements
The author thanks everyone who has ever had to explain why “Critical” does not automatically mean “fix this before lunch.”
Author’s Address
Standards Desk
Somewhere on the Internet