Hacker news

  • Top
  • New
  • Past
  • Ask
  • Show
  • Jobs

Someone reported java4shell bug in September 2026 (https://github.com)

445 points by notmine1337 1 day ago | 128 comments | View on ycombinator

black3r about 22 hours ago |

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

dlor about 13 hours ago |

I also found this independently ahead of disclosure and reported it to Oracle last Friday. My harness found it after a fuzzing run and then turned it into a full RCE chain in the target app I was actually scanning.

The harness itself doesn't run with Internet access and I confirmed it didn't access this PR directly, but who knows if this was in the training set itself.

Either way, these simultaneous disclosures are incredibly common now. The Ruby issue affecting Gitlab was not only known about for 6 months, it was publicly fixed for 6 months before someone turned it into an RCE. The fix sat on the Ruby dev branch, and it was never pulled into an actual Ruby release until after Gitlab disclosed their own 10.0 vulnerability through it.

It's very common for reporters to not realize the impact of a bug, models are very good at turning bugs into RCE chains, and the volume everywhere now means security teams are basically only focused on RCEs.

wood_spirit about 23 hours ago |

So the implication is that the LLM that assisted the Calif researchers might have read this previous bug report and not independently discovered it?

Botifier about 19 hours ago |

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

kccqzy about 19 hours ago |

Even earlier. The bug, SIGSEGV, was reported back in June. The original reporter isolated it to base64 in September.

https://github.com/adoptium/adoptium-support/issues/1480

darkamaul about 23 hours ago |

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

elashri 1 day ago |

This person is a member of OpenJDK organization and a contributer but not sure if he is oracle employee.

rzmmm about 23 hours ago |

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

undefined about 19 hours ago |

undefined

InsidiousWombat about 23 hours ago |

Nice 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 1 day ago |

It's even titled buffer overflow.

yread 1 day ago |

They even used the same example as Calif: AAA....A=.

stevefan1999 about 5 hours ago |

Sigh. We are getting less secure in the age of AI due to bureaucracy. I'm tired to patch it one by one, please unleash hell on earth for me to end this once and for all

badgersnake about 18 hours ago |

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

panny about 5 hours ago |

>AI regurgitates another human solution

lol

lmao even

frankregis about 7 hours ago |

Bu9ongio

farceSpherule about 17 hours ago |

[dead]

pepegroxxouceda about 19 hours ago |

[dead]