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/
Risk is not what the CVSS score measures, correct. However the CVSS base score is first and foremost a measure of severity (of the vulnerability). I think they were being loose with their terminology when they wrote "severity is low" and probably meant to say "risk".
The spec talks about this in depth. Paraphrasing: The base score captures intrinsic characteristics of the vulnerability assuming a (reasonable) worst-case configuration.
It's a measure of "How screwed am I if I'm using this software in this specific-but-reasonable manner?", it's not a measure of "How screwed is everyone using this software?".
P.S. I broadly agree, just adding a minor correction on the terminology.
And CVSS v4 does add criteria that let's the provider specify how urgent it is, if it can be automated, etc.
I think the bigger problem is that the scoring system lets you specify a small number of factors and still reach a 10.0, and all the optional and supplemental factors reduce it. Like if you try to enter this vulnerability into v4 and fill out more factors, you easily drop it into the 8s.
So essentially everyone submitting the vulnerability is doing the bare minimum, contributing to the perception that the scores are inflated.
And then people don't use the current version of the score. CVSS 3.1 came out in 2021. CVSS 4.0 came out in 2023. Why the hell is everyone still using 3.1?
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.
If you want a quick overview of the risk: CVE-2026-121481 is listed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H which is what calculates the CVE score. This is missing the temporal/environmental components (which rarely ever seems to get entered).