Java4Shell: RCE in OpenJDK when processing Base64

werrett 719 points 192 comments November 17, 2026
calif.io · View on Hacker News

Discussion Highlights (19 comments)

plmpsu

Does anyone know what the attack vector of this is? I'm trying to figure out if our usage is affected by this CVE.

AgentME

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 )

benjiweber

https://github.com/openjdk/jdk/commit/5177a70b385c16f26ede19...

leca

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.

ievans

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.

mzs

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.

doctorpangloss

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?

Sigmazero60

We set UseAVX=2 on all our jdk hosts last year for unrelated thermal issues, turns out that saved us here

eyalitki

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.

nacnud

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.

kaliszad

Seems like -XX:-UseBASE64Intrinsics is the better workaround for now.

yabones

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

hypfer

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?

nikanj

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?

dboreham

"vibe-uncoding" -- have actually been doing quite a bit of that in my older projects.

secondcoming

Why would anyone write the scalar part of a SIMD'd function in assembly code!?

iririririr

is this why half the banks worldwide are offline on and off since yesterday?

cedricbonhomme

Tracking sightings related to this vulnerability here: https://vulnerability.circl.lu/vuln/CVE-2026-114938#sighting...

rbanffy

Not everywhere... Requires an x86-64 processir with AVX512.

Semantic search powered by Rivestack pgvector
13,334 stories · 126,150 chunks indexed