Elektrine lite

← Feed

@jgamblin@infosec.exchange

2026-07-28 14:25 UTC

CVSS is a severity label the industry treats like a priority list. A 9.8 tells you how bad a bug could be. It cannot tell you which 9.8 to do first. This year 4,719 CVEs carry a CVSS v3 score of 9.0 or higher. Half of them, 2,493, land on the identical 9.8, the arithmetic result of a remote, unauthenticated, full-impact vector. Nine distinct scores exist in the entire critical band. There is no 9.5 and no 9.7. That is the resolution you are triaging with. Rank the same 4,719 by EPSS percentile and the median lands at the 37th, so half the drop-everything tier ranks below 63% of all CVEs. Cut at the 90th percentile and 211 CVEs hold 49 of the 54 now on CISA's KEV list. One caveat: EPSS reads exploitation signal, and all 54 were listed before these scores were computed, so that is two sources agreeing, not a prediction. It still gives you an order. 9.8 does not. 2,493 CVEs this year share one score. If your tooling had to put them in a fix order tomorrow morning, what field would it sort on, and who would argue with you about it? #vulnerabilitymanagement #cybersecurity #CVE

Replies (2)

  • @darakian@fosstodon.org 2026-07-28 16:26

    @jgamblin@infosec.exchange I would suggest that if we as an industry want to be able to construct priority lists then prescribed severity is simply the wrong model. Severity should be derived based on the CVE record consumers environment.

    Open ##5220681

  • @eckes@zusammenkunft.net 2026-07-28 18:07

    @jgamblin@infosec.exchange it’s even worse, many 10.0 scores might not even apply to you and a 6.5 can start a chain to be owned

    Open ##5220682