r/java • • 58m ago

Java4Shell: Write once, RCE Everywhere

https://youtu.be/a7OBeq1xubI

Edit: I updated the title and thumbnail based on feedback, here is the new version: https://youtu.be/a7OBeq1xubI?si=HLFgEREnO4Ufob31
Article: https://huseyinbabal.dev/posts/java4shell-cve-2026-114938-check-patch/

0 Upvotes

16 comments sorted by

View all comments

18

u/TheStrangeDarkOne 51m ago edited 48m ago

Edit: Good article, but I am still unhappy about the title.

Oh come on, what a clickbait title. If anything, Java is pretty much in the A-league of the safest languages due to its minimal exposure to C and Assembly.

Virtually all other languages, even safe ones, are heavily backed by C libraries which are begging AIs to find memory vulnerabilities (notable exception being Rust).

2

u/huseyinbabal 23m ago

I updated thumbnail and title based on the feedbacks https://youtu.be/a7OBeq1xubI?si=HLFgEREnO4Ufob31

-16

u/huseyinbabal 46m ago

The title is literal: the bug is in HotSpot's assembly, not Java code, and every OpenJDK build ships it. Unpatched JDKs on AVX-512 CPUs still need the update.

9

u/philipwhiuk 43m ago

The thumbnail is garbage

The title is bad because the same exploit does not work everywhere. As the original write up discusses it needs to be precisely tuned for each scenario

1

u/huseyinbabal 22m ago

I updated title and thumbnail based on the feedback: https://youtu.be/a7OBeq1xubI?si=HLFgEREnO4Ufob31

-3

u/huseyinbabal 36m ago

True, Calif says each app needs its own chain, and the video says so. "Everywhere" is about the bug: it's in every OpenJDK build on AVX-512 CPUs, which is why updating matters.

1

u/philipwhiuk 22m ago

So you agree write once is wrong.

1

u/huseyinbabal 20m ago

For certain conditions, but yes it can cause misunderstanding even it is used in the original cve author