logoalt Hacker News

jeroenhd • today at 1:16 PM • 2 replies • view on HN

CVSS scores do not indicate priority. They give a baseline so you can pick what CVEs affecting you you should do risk analysis for first.

The score is just fine. The people misinterpreting everything with a CVSS score higher than 8 as the end of the world are panicking over nothing.


Replies

da_chicken • today at 1:56 PM

This. It's a calculated score based on pretty objective measures. Yes, the CVE[0] notes that "The severity is Low because no attacker-controlled path to the overflow is known."

But risk or severity is not what CVSS measures. It's a score intended for security professionals who know the context, graded against a fixed algorithm, with a fixed definition for each answer. The nvd.nist.gov site isn't always the easiest to use, so grab a good CVSS calculator[1] and look at what it means. That's why the alphabet soup vector string is there: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

I'm sorry, CVSS wasn't meant to eliminate your need to think or understand your environment. Yes, if it's a 9.8 CVSS you should look at it. Triggering you to look at it is all the CVSS is meant to do!

Now, whether you think CVSS scores mark too many things as High or Critical is a little secondary. There is a reason we're at CVSS v4. Defining metrics and keeping them useful while remaining objective is difficult. This vulnerability, however, is exactly the kind a chain exploit would take advantage of.

[0]: https://www.cve.org/CVERecord?id=CVE-2026-121481 [1]: https://www.metaeffekt.com/security/cvss/calculator/

➕ show 1 reply
npongratz • today at 1:41 PM

> The people misinterpreting everything with a CVSS score higher than 8 as the end of the world are panicking over nothing.

They are indeed, but that means CVSS has turned into a trigger for The Boy Who Cried Wolf. So we need a different metric. The problem, of course, is that adding a new score creates an xkcd 927 issue.

➕ show 1 reply