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.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.
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)
Their video of the exploit in action would be stronger if it was a bit more straightforward.
All the (impressive!) distracting graphics, the speed of change, and the lack of commentary meant it took me a few watches to actually notice the ‘seashell’ segments were wrapping remote shells that the exploit had given them.
>The best hacker today is neither AI nor human. It is the centaur hacker, part human, part AI.
I think only really smart people are going to be left in Security and Software. I can barely fathom what this group is doing with AI right now (ignoring that their model probably isn't nerfed and mine would be) and I don't think any of this is trainable for the average developer. This is starting to feel like some of the scientific fields where careers start when you get a MS/PhD. Or like the average developer is on the same level of not being able to convert a Word document to PDF.
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.
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.
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.
This thread on the Temurin project is worth a read too: https://github.com/adoptium/temurin/issues/326
Bummer that:
> The Eclipse Foundation is not in the Vulnerability Group (despite their request to join), so we do not get weeks of advance notice regarding CVEs and patches (which would essentially allow us to build & test in advance of an embargo being lifted, and deliver on hour zero).
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.
This attack surface (manually optimized assembly code in the middle of software stacks) looks AWESOME
Eclipse Temurin has not released a patch yet....
(Re-reading my comment, sounds like I'm throwing shade. I was just trying to state a fact. In fact most of the third party distros have been caught off guard).
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?
Perhaps its time to eclipse JIT + heap based complex memory allocation algorithm runtimes like java? Now that AI can port code to other safer/better systems like rust. The "simpler" the memory management system is the easier it is to harden against such attacks.
This attack is pretty insane to me for a couple of reasons. That intrinsic implementation is compiler/runtime dependent. There are many implementations of JVMs out there that could be vulnerable.
The other scary thing is that there are likely other intrinsic implementations which hide vulnerabilities that are hard to know without further research.
Not even fuzzing these things are criminal in 2026.
Is it difficult to just go through Java, nodejs etc. Base64/hex/.. implementations and fuzz them all?
Does anyone know why this would be missed?
I see no security advisory from Elasticsearch yet,we operate multiple ES clusters and I am not exactly sure what the mitigation is here. Changing our JVM options and restarting the nodes?
"Since bzhiq(-1, output_len) doesn’t change any bits if output_len >= 64, this results in output_mask == -1u64."
Should say "output_len & 0xFF >= 64" instead. Bzhi only looks at the bottom byte.
Seems like -XX:-UseBASE64Intrinsics is the better workaround for now.
This only fires on x86 servers whose CPUs have AVX-512 VBMI. ARM boxes like Graviton and older Xeons never run the buggy code.
Could this be what triggered the recent outages?
Why pair Spock with All Your Base? It was CATS that said the line.
Not everywhere... Requires an x86-64 processir with AVX512.
> It took our own Quang Luong an hour to discover the vulnerability, and two more hours to develop the first working exploit. The total token cost was less than $200.
I don't know, man. I just don't know.
This looks like it requires G1? ZGC, ParallelGC or Serial are not affected? Smaller workloads running on singe CPU containers would default to Serial GC.
Does anyone know what the attack vector of this is? I'm trying to figure out if our usage is affected by this CVE.
Why would anyone write the scalar part of a SIMD'd function in assembly code!?
Tracking sightings related to this vulnerability here: https://vulnerability.circl.lu/vuln/CVE-2026-114938#sighting...
Does the JIT compiler not do a good enough job at optimizing code that can take advantage of SIMD to just use java code for base64?
It seems like ARM64 AArch64 instances are not affected.
internet is a terrifying place right now i wonder what exploit hackers knows about, but its not publicly available now
Is this supported in Minecraft on FEX?
The string of A's reminds me of the ssh exploit recently.
is this why half the banks worldwide are offline on and off since yesterday?
"vibe-uncoding" -- have actually been doing quite a bit of that in my older projects.
Encode binary data in text because some dumb thing can't process binary. Text back to binary slow, so better make use of ridiculously wide vector width thing to speed up dumb decoding step we should have never become reliant on in hot paths. Derp, memory safety bug. Derp, die because performance "optimization".
Our incredibly high tower of Jenga blocks is falling down under its own weight.
So many promotions because of optimizing cosmically unnecessary work, though.
Derp, derp, this is humans making computers.
As a person who does these kinds of optimizations, it hits in the feels.
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. :(
That Vibe Uncoding section didn't go where I thought it was going. Instead of suggesting people stop vibe coding and potentially introducing more/new vulns, they suggest vibing the removal of features and hoping the model or the tests it generated or whatever catch the edge cases. It really does feel like we're circling the drain here, folks.
Also, (S)FTP is dead? Since when?
New rule: all hand-written SIMD routines must be formally verified.
Hand-rolled assembly for base64 decoder seems like a great place to plant a backdoor. Wonder who wrote this.
Uuuu, bug and exploits part is pretty standard so becomes boring wall of text that is instantly obsolete after patches, I hope ;) And no animation ?? How hard it is to splash there some animation ?? ;)
But there is part of article that somehow nobody mentions ! "A call for vibe-uncoding" and that is a future and sane sanity. How many unused Linux modules laying on disk ? And more commercial systems are usually worse - installer just unpacks and declares warranty void if something is modified or removed - law enforced stupidity.
You have [open] code ? You can clean it by doing very coarse work of not calling unused code or hardcoding return error on calling unused parts.
Like FTP code. Open source IT declared it dead years ago but camera and game manufacturers and probably more industries didn't get a memo. Still we do not implemented ftp replacement and ssh is single point of failure.
This is the code I use since 20 years back:
http://move.rupy.se/file/base64.txt
If this part becomes the bottleneck; so I need to write a GPU accelerated version I'll eat my own hat.
> "It is the centaur hacker, part human, part AI."
AI is... a horse?
Calif is the new Gobbles. IYKYK.
Seems like security through obscurity might be a thing after all.
The risk owners, security teams, compliance teams - are all holding tight inside a tent built for the usual weather, but facing an un-announced storm now.
Their first priority is not stabilizing the tech tent. They are busy planning the risk distribution, risk outsourcing, legal prep, customer messaging, ToS/SLA reviews, contracts etc. They are reinforcing the good-old fort walls around the tech tent.
From the section on performing heap grooming over the network ("Remote Heap Feng Shui"):
> The current attack is sensitive to network conditions, like RTT and jitter. Low, stable round-trip times are preferred for a more reliable attack. In our controlled environment, we performed this attack over the internet through public IP addresses instead of just assuming perfect laboratory conditions. For the current attack path to achieve optimal stability and reliability in exploitation, Calif turned to physics and utilized money to solve the problem, rather than experimenting with TCP/IP stack configuration. In other words, Calif rented another VM in the same region as our target.
And the "Limitations" section:
> There is no universal payload. Each chain needs a decoder route, a live writer, a returned reader or another feedback path, a heap layout, and an application action. Every target needs a bespoke profile. The exploit is not a universal point-and-shoot.
Based on the complexity and constraints, short-term mass-exploitation seems unlikely. It will take some time before there are reliable exploits, and they may require running on infra close to the target.
But a long tail of unpatched java applications/services at high-value targets getting exploited, seems plausible to me.