Java4Shell: RCE in OpenJDK when processing Base64

229 points - today at 9:11 PM

Source

Comments

ievans today at 9:23 PM
Super impressive work by Calif as usual.

The exploit conditions are very specific but there are still going to be a lot of hosts impacted. We at Semgrep published some free detection scripts here: https://github.com/semgrep/detection-scripts/tree/main/CVE-2...

They look for these five conditions:

  * HotSpot VM: any OpenJDK build, Oracle JDK, or GraalVM JDK. Only HotSpot generates the stub. OpenJ9 and GCJ are OK. Azul Prime (Zing), which replaces C2 with its own JIT, and any VM name not recognized as HotSpot are [?], never [!].
  * x86-64 JVM on an x86-64 host.
  * Version 17.0.6 or later, not at or above a version listed in FIXED_IN, and no newer than the newest releases checked (see below). Newer versions are [?]: they may carry the fix.
  * The JVM reports avx512_vbmi and avx512bw, and UseAVX >= 3.
  * Base64 intrinsics are on and C2/JVMCI can compile. These turn it off: -XX:-UseBASE64Intrinsics, -XX:DisableIntrinsic=_base64_decodeBlock, -Xint, -XX:TieredStopAtLevel below 4.
leca today at 9:19 PM
What’s that old Chinese proverb? “May you live in interesting times”? It feels like we’re living in interesting times. How long will it take for a bad actor to seriously compromise critical infrastructure? My bet is within six months.

The upside is that it’ll force legacy institutions and organizations with sub-par security to get good at security and modernize their legacy stacks. That, or get pwned in short order.

drum55 today at 10:08 PM
They aren’t wrong that we should be deleting more support and removing more features. The idea that the linux kernel by default builds support for all sorts of ancient systems nobody has ever heard of is absurd.
AgentME today at 9:08 PM
Unconfirmed, but people on Twitter suggest this vulnerability has to do with the AVX512 implementation of Base64 decoding, and so this vulnerability can be worked around by running Java with the -XX:UseAVX=2 flag. (https://x.com/sean_a_cassidy/status/2122791344573976817)
mzs today at 9:25 PM
You can also mitigate Java4Shell by starting OpenJDK with either:

-XX:-UseBASE64Intrinsics to disable hardware-accelerated Base64 encoding and decoding, or

-XX:UseAVX=2 to disable AVX-512. Apply this flag only on x86-64 hosts. OpenJDK on ARM doesn't recognize it and will fail to start.

nacnud today at 9:37 PM
More info here: https://www.upwind.io/blog/java4shell-what-we-know-now-and-w...

It's a heap out-of-bounds write in Java’s AVX-512 Base64 decoder.

spidermonkey23 today at 10:43 PM
The string of A's reminds me of the ssh exploit recently.
yabones today at 9:40 PM
Before you keep your security team up all night, it looks like proxies save the day here. Might not be a complete fix, obviously a real patch should be applied as soon as possible.

> Request streaming. Some current grooming profiles need partial request bodies to reach the application. A proxy that waits for the complete body removes their release timing. nginx buffers request bodies by default.

https://calif.io/java4shell/#limitations

Noe2097 today at 10:20 PM
This attack surface (manually optimized assembly code in the middle of software stacks) looks AWESOME
rbanffy today at 10:04 PM
Not everywhere... Requires an x86-64 processir with AVX512.
hypfer today at 9:51 PM
Given that this is AVX512-only...how many enterprises are out there that run vulnerable java applications on non-intel servers?

Genuine question. Everything I see is Intel all the time. I know that people at home switched to AMD, but they don't run enterprise java.

I also have been told that apparently EPYC was hyped for a while and some hosters give you that. But do corporations run the java applications there?

The name makes it sound like Log4J or the PHP thing, but from what I can tell right now, it kinda isn't all that relevant?

cpach today at 9:52 PM
.
fidotron today at 10:15 PM
This will almost certainly in practice affect a majority of Java app servers in production.

What makes it nasty is triggering it could be done so easily by url decoding, sending an email or many other things.

kaliszad today at 9:38 PM
Seems like -XX:-UseBASE64Intrinsics is the better workaround for now.
cedricbonhomme today at 10:03 PM
Tracking sightings related to this vulnerability here: https://vulnerability.circl.lu/vuln/CVE-2026-114938#sighting...
mushufasa today at 10:07 PM
where is the dancing girl in the exploit videos???
DarkmSparks today at 10:32 PM
me using java for so long I have my own util.Base64 class used everywhere in pure java.

now panicking in case some LLM imported this without me noticing.

edit: it did. :(

9029 today at 10:40 PM
So who leaked it?
plmpsu today at 8:36 PM
Does anyone know what the attack vector of this is? I'm trying to figure out if our usage is affected by this CVE.
jeffbee today at 10:36 PM
If I owned an entire language platform with a JIT, it would not contain assembly in its standard library, it would simply be improved until it generated something at least that fast from high-level source code on that target CPU.

This is something I really like about LLVM. Their libc isn't spilling over with hand-written assembly. It's written in straightforward C++ under the belief that the compiler does, or will do, a good job.

nikanj today at 9:52 PM
Just as with CVE-2026-98432, Debian is immediately patched at embargo drop, Ubuntu still isn't patched.

Why do we even pay for Ubuntu?

iririririr today at 9:59 PM
is this why half the banks worldwide are offline on and off since yesterday?
secondcoming today at 9:57 PM
Why would anyone write the scalar part of a SIMD'd function in assembly code!?
dboreham today at 9:53 PM
"vibe-uncoding" -- have actually been doing quite a bit of that in my older projects.
doctorpangloss today at 9:27 PM
is this the root cause of the issue befalling making giant companies right now? i think it's a java DOS for sure, but an RCE?
deleted today at 9:24 PM
deleted today at 9:53 PM
nassirkhan today at 10:45 PM
[flagged]
Sigmazero60 today at 9:32 PM
We set UseAVX=2 on all our jdk hosts last year for unrelated thermal issues, turns out that saved us here
spullara today at 10:28 PM
please stop using native code that hasn't been proven
eyalitki today at 9:36 PM
The fact that mainstream modules have such trivial bugs in logic that can be fully covered by testing is staggering. It is about time software developers will have proper test coverage for their code, at least for basic "unit" modules. Maybe we can even name a testing philosophy to match it.