News for hackers. Stuff that matters.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by jtrn on Friday November 20, 2026 @06:27AM (#50573211)
THIS!!!!!!!!!!!!!!! THIS times 10000!

I'm starting to get annoyed about the OMG OMG BREAKING BREAKING ALARM-EMOJI crap that's not a real emergency.

Four times in the last month, I dropped everything and started investigating whether a serious CVE related to any of our dependencies warranted an emergency bump, only to be frustrated that images, even from AWS, did not have the fix yet. So then I had to worry about whether I should build from source. We actually built PHP from source and deployed it to prod, just to get ahead of the PHP2Shell vulnerability

But yesterday's PHP vulnerability, CVE-2026-115560, didn't even apply to us or most people running PHP, and I don't think there are any realistic working exploits out there. I'm not saying that it's not possible, but I'm starting to feel that there's a large difference between what's theoretically possible and what's practically possible. And given the storm of patches and vulnerabilities found, this will become increasingly important to ask.

I think everything above a CVE score of 9.0 should warrant some level of “how exploitable is this in real life,” and anything above 9.5 should be proven to be easy for an attacker to execute, not just “possible in theory.” I don't see how we will survive as developers if there isn't some sort of better triage for vulnerability severity assessment. If everything is an emergency, then nothing is an emergency.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by stingraycharles on Friday November 20, 2026 @08:32AM (#50574410)
Yes, and this also causes inertia, as if everything is super highly critical it means nothing is, and people will stop caring when something is actually serious.

Heartbleed, Spectre, log4shell, they were all worthy of a 9.8.

This isn’t.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by ylk on Friday November 20, 2026 @09:50AM (#50575431)
There are more values in the CVSS vector you can fill in yourself: environmental and threat scores

So you can take e.g. a 9.3 critical down to 6.5 medium by setting CIA requirements to low and exploit maturity to Unreported.

I’m not saying CVSS is perfect but if you want to have a score that applies to your environment, you have to input some info about your environment into it.

“how exploitable is this in real life” is answered by the exploitability score, which is calculated from Attack Vector, Attack Complexity, Attack Requirements, Privileges Required, and User Interaction scores.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by jtrn on Friday November 20, 2026 @11:01AM (#50576745)
Good info, thanks.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by dboreham on Friday November 20, 2026 @10:35AM (#50576256)
Yes. Lots of this. E.g. the nginx flap yesterday depended on http/2 being enabled, which it isn't by default. AI can be helpful with the analysis though.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by guipsp on Friday November 20, 2026 @12:57PM (#50579009)
No one runs nginx in the default configuration