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.
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.