Re:Java4Shell: RCE in OpenJDK when processing Base64
by adrianpike on Tuesday November 17, 2026 @05:21PM
(#50539090)
Instability is often correlated to urgently performed change, and we've seen a lot of instability around the world lately.
[ Parent
| on HN ]
Re:Java4Shell: RCE in OpenJDK when processing Base64
by pixl97 on Tuesday November 17, 2026 @05:32PM
(#50539212)
A lot of organizations we sitting on internal bugs for years because they thought they were impossible to exploit, and now their red team can break them in hours.
Most businesses are stuck in a trap now. They know the software is exploitable, but they are organizationally slow in testing and rollout. They have to start moving fast with security and IT organizations that are cut to the bone, yet at the same time contain to much box checking deadweight.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by jeremyjh on Tuesday November 17, 2026 @06:37PM
(#50539792)
3/4 of the Fortune 500 will conclude they should hire expensive consultants to create more checkboxes.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by ChuckSneed on Tuesday November 17, 2026 @05:33PM
(#50539226)
Instability can also be attributed to AI slop code. That's the simplest explanation.
Re:Java4Shell: RCE in OpenJDK when processing Base64
by thephyber on Tuesday November 17, 2026 @08:27PM
(#50540705)
I don't think AI slop code is the proximal cause for most of this. It is, however, the most common meme for blame.
My suspicion is (1) company execs are being told to expect company extinction if they don't force faster velocity and (2) we are increasingly building more and more complex systems, so neither AI nor humans can find all of the issues before they cause outages.