Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by raizer88 on Friday November 20, 2026 @02:02AM
(#50571103)
Don't tell me. I work for a bank and we have automated vuln checks on our code and dependencies and we can't release in pre-prod if we don't fix the cves. Basically since last year is 1 day you deploy new code and 2 days you deploy cve fixes.
[ Parent
| on HN ]
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by jve on Friday November 20, 2026 @02:40AM
(#50571394)
That's a great process for a bank!
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by toenail on Friday November 20, 2026 @08:05AM
(#50574146)
The problem with "must fix CVEs" is that it's stupid, as most CVEs will never be a problem unless somebody alredy broke into your server. Yes, yes, security comes in layers, but the security circus is also a reality.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by dboreham on Friday November 20, 2026 @10:39AM
(#50576337)
It's also a denial of service attack on your brain because you have to do the work to prove to some beurocrat that the vulnerability can't be exploited in your environment. It usually turns out to be easier to just take the fix. And then of course we get the production downtime events because the fixed versions have other new bugs.