The fact you need such a large payload should be triggering all sorts of alerts. I’d be more worried about the fact if you have these alerts in place, rather then this specific vulnerability.
OpenSSL base64 bug (CVE-2026-121481): the 9.8 is overblown.
It needs about 1.6 GB of input in one call; the only known trigger is a huge openssl s_client proxy password you set yourself. The 9.8 is CISA's, not OpenSSL's. Next patch cycle.
https://t.co/9QhFvUTZGz
@HackingDave Slight correction, it causes chaos in pretty much most companies. Staff are already maxed out and these unnecessary BS findings are making a tough job even harder. The volume is simply not sustainable.
I���m not one for the whole AI hype train. But there’s no denying that it’s significantly shifting things. I wouldn’t say it’s changing things in the sense of new wild findings. What it is doing is significantly increasing the volume of findings, along with significantly reducing the barriers and time to be able to exploit those findings.
Security = Manage/Reduce Risk
Risk = Likelihood * Impact
CVSS does cater much for likelihood, and I know that you’ve pointed this out in the past.
A large asteroid hitting the earth is a pretty bad thing. Impact (literally) is huge, but likelihood is very very low. Hence why we don’t spend our days worrying about being taken out by a large asteroid 😁
With the increase in volume of the number of vulns being identified by AI, you have to start leveraging AI to help determine if/how you are affected. Trying to keep up manually now is likely not going to scale with the increasing pace that these vulns are coming out at. Not to mention how many are now being leaked before the fix is actually available.
Pre-auth RCE in nginx is the bug every hacker dreams of finding. It almost never happens.
Today we’re disclosing nginx2root: five nginx vulnerabilities, and an exploit that takes an unauthenticated attacker all the way to root.
One of themhits the default config.
If you run nginx, patch now. Then read: https://t.co/rDQQAimLZP
CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425