Java4Shell is a reason to use Java
15 comments · java, security
- Comments15
15 comments · java, security
Story details from Lobsters ↗ · linked article on mccue.dev.
Java4Shell is a reason to use Java was first seen on Lobsters · Hottest on Nov 18, 2026. Since then it has appeared in 74 checks on 3 different days. Its best position was #2 of 25, reached on Nov 18, 16:51 UTC. It is #17 right now, holding steady at #17 over the last 6 checks.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
▲ as reported by Lobsters.
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
The point seems to be that entire classes of security violations generally do not exist in Java (which is true), not that security violations do not exist in Java. It seems a reasonable point.
Ehh as someone that likes Java I don’t really buy this. There have been plenty of RCEs unrelated to memory safety, the biggest one being the log4j one from a while ago. There were also a decent number of Jackson/native serialization ones that happened over the years. Sure a majority of the time it’s libraries that…
The native code protections apply to JNI. The difference between the JVM and other ecosystems is that you will need to opt-in even if the JNI comes from a transitive dependency.
Archived daily, weekly and monthly lists that include this entry.
Yes. As of Nov 20, 03:52 UTC it is #17, holding steady at #17 over the last 6 checks.
#2 on Lobsters · Hottest, on Nov 18, 16:51 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 18, 2026 and has been on the list on 3 days (74 checks) since.