Someone reported java4shell bug in September 2026
- black3r - 16587 sekunder sedanThe very first referenced issue in that PR discussion sheds a bit more light on this: https://github.com/adoptium/adoptium-support/issues/1480
This PR's author says there on October 1st: "Got an email from Oracle asking me to NOT proceed with a PR until receiving approval." and then on October 28th: "It's taken over by Oracle. Nothing required from us."
- wood_spirit - 20761 sekunder sedanSo the implication is that the LLM that assisted the Calif researchers might have read this previous bug report and not independently discovered it?
- darkamaul - 18545 sekunder sedanWe will never know, but there is a chance that the Calif's researcher model decided to look at the open and closed issues / PRs of the repo.
Nonetheless, being able to understand the criticality of a finding, and how to exploit it are other skills, that still require supervision.
- Botifier - 4759 sekunder sedanOracles comment for the merged commit is the exact same as in that PR word for word: https://github.com/openjdk/jdk/commit/5177a70b385c16f26ede19... https://github.com/openjdk/jdk/pull/32781/changes/d2f942c478...
- rzmmm - 20533 sekunder sedanFrom califio: "I focused the audit on the JIT compiler, intrinsics, widely accessible APIs, and cryptography. Well, more precisely, I told Codex to look at those areas like any serious security researcher in 2026."
Maybe simply a coincidence, but I would put my bets that the first person with the PR was also using Codex, and the model was exposed to the details of the bug.
- kccqzy - 5210 sekunder sedanEven earlier. The bug, SIGSEGV, was reported back in June. The original reporter isolated it to base64 in September.
- elashri - 25684 sekunder sedanThis person is a member of OpenJDK organization and a contributer but not sure if he is oracle employee.
- InsidiousWombat - 20360 sekunder sedanNice proof that the auto-close bots are literal cancer on project that make stuff worse.
It was literal bug with provided fix. All it needed is someone to have a proper look.
But someone clowned a bot under a visionary thought "if nobody looked it must not be important" and here we are
- fulafel - 23225 sekunder sedanIt's even titled buffer overflow.
- yread - 23601 sekunder sedanThey even used the same example as Calif: AAA....A=.
- - 5603 sekunder sedan
- badgersnake - 946 sekunder sedanMuch easier to scrape the closed PRs with your LLM than actually do proper analysis I guess.
Although maybe they didn’t even know their LLM was doing this.
- pepegroxxouceda - 3669 sekunder sedan[dead]
Nördnytt! 🤓