Someone reported java4shell bug in September 2026
103 comments
- Points370
- Comments95
103 comments
Story details from Hacker News ↗ · linked article on github.com.
Someone reported java4shell bug in September 2026 was first seen on Hacker News · Front page on Nov 19, 2026. Since then it has appeared in 57 checks on 2 different days. Its best position was #8 of 30, reached on Nov 19, 15:44 UTC. It is #15 right now, slipping from #10 to #15 over the last 6 checks.
Position on Hacker News · Front page at every check (lower is better).
Best rank per day (UTC).
points as reported by Hacker News.
A few top-level comments from Hacker News, shortened. Read the full thread on Hacker News.
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,…
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…
So the implication is that the LLM that assisted the Calif researchers might have read this previous bug report and not independently discovered it?
Archived daily, weekly and monthly lists that include this entry.
Yes. As of Nov 20, 03:44 UTC it is #15, slipping from #10 to #15 over the last 6 checks.
#8 on Hacker News · Front page, on Nov 19, 15:44 UTC. Trendoday checks this list every 15 minutes.
It was first seen on Nov 19, 2026 and has been on the list on 2 days (57 checks) since.
370 points and 95 comments; submitted by notmine1337 on Nov 19, 2026.