News for hackers. Stuff that matters.
Re:Someone reported java4shell bug in September 2026 by elashri on Thursday November 19, 2026 @08:48AM (#50560071)
This person is a member of OpenJDK organization and a contributer but not sure if he is oracle employee.
Re:Someone reported java4shell bug in September 2026 by egorfine on Thursday November 19, 2026 @10:07AM (#50561096)
None of this did help: nobody gave a flying f.
Re:Someone reported java4shell bug in September 2026 by bobmcnamara on Thursday November 19, 2026 @10:13AM (#50561166)
Someone probably gave a maintainer "the talk"
Re:Someone reported java4shell bug in September 2026 by pron on Thursday November 19, 2026 @03:46PM (#50566123)
There were no public comments precisely because it was immediately identified as a potential security risk! The JDK is so critical and sensitive (probably the most important open source project after Linux) that we have policies that are more carefully considered than your normal open source project. We can allow no public comments and no public merges of code on anything that could be a security risk before the security research team studies it.
Re:Someone reported java4shell bug in September 2026 by egorfine on Thursday November 19, 2026 @03:49PM (#50566158)
That makes sense!
Re:Someone reported java4shell bug in September 2026 by karianna on Thursday November 19, 2026 @04:13PM (#50566457)
^^This. Same policy was applied at Adoptium once we realised what it might entail. Oracle did the right thing here in my estimation
Re:Someone reported java4shell bug in September 2026 by hobo123 on Friday November 20, 2026 @01:11AM (#50570787)
Right thing would have been disabling the fast path intrinsic and releasing that right away, with a CVE.
Re:Someone reported java4shell bug in September 2026 by pron on Friday November 20, 2026 @09:04AM (#50574823)
That would be the wrong thing to do. You don't know how severe the problem is and what to advise your users. Important products like this have regular quarterly updates, where the less risky vulnerabilities are patched. You can't just cut an emergency release that your users may not be prepared to apply before you know what the risk is.
Re:Someone reported java4shell bug in September 2026 by Phelinofist on Thursday November 19, 2026 @04:22PM (#50566555)
So reports without any activity are the juicy stuff? Got it /s
Re:Someone reported java4shell bug in September 2026 by pamcake on Thursday November 19, 2026 @10:21PM (#50569756)
That's all good by itself. However, in my view the original PR on September 9 should be seen as a public disclosure in itself. When a security vulnerability becomes public like this (regardless of why or by whom), that should have impact on timeline for fix, and maybe also communications. The cat's out of the bag already and no amount of silence will put it back in.

A lot of similar aspects to the "PHP embargo was broken" deal the other week.

For the same reasons you give, there is a different level of pressure on timelines and responsiveness, too, for a project like OpenJDK. I don't think 1 month is reasonable timeline for a publicly known vulnerability like this.

Re:Someone reported java4shell bug in September 2026 by staplehorse6553 on Friday November 20, 2026 @03:26AM (#50571757)
>probably the most important open source project after Linux

That's a wild thing to say about my Minecraft server, but I appreciate the concern!