Main thread here: https://news.ycombinator.com/item?id=50532118
What’s that old Chinese proverb? “May you live in interesting times”? It feels like we’re living in interesting times. How long will it take for a bad actor to seriously compromise critical infrastructure? My bet is within six months.
The upside is that it’ll force legacy institutions and organizations with sub-par security to get good at security and modernize their legacy stacks. That, or get pwned in short order.
Why would anyone write the scalar part of a SIMD'd function in assembly code!?
You can also mitigate Java4Shell by starting OpenJDK with either:
-XX:-UseBASE64Intrinsics to disable hardware-accelerated Base64 encoding and decoding, or
-XX:UseAVX=2 to disable AVX-512. Apply this flag only on x86-64 hosts. OpenJDK on ARM doesn't recognize it and will fail to start.
Just as with CVE-2026-98432, Debian is immediately patched at embargo drop, Ubuntu still isn't patched.
Why do we even pay for Ubuntu?
"vibe-uncoding" -- have actually been doing quite a bit of that in my older projects.
[dead]
The fact that mainstream modules have such trivial bugs in logic that can be fully covered by testing is staggering. It is about time software developers will have proper test coverage for their code, at least for basic "unit" modules. Maybe we can even name a testing philosophy to match it.
Super impressive work by Calif as usual.
The exploit conditions are very specific but there are still going to be a lot of hosts impacted. We at Semgrep published some free detection scripts here: https://github.com/semgrep/detection-scripts/tree/main/CVE-2...
They look for these five conditions: