News for hackers. Stuff that matters.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by dns_snek on Friday November 20, 2026 @10:19AM (#50575902)
[delayed]
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by da_chicken on Friday November 20, 2026 @10:56AM (#50576657)
Exactly, yes.

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?