November 18, 2026
Java4Shell (CVE-2026-114938): The Pre-Auth RCE That Wants to Break Your Enterprise Stack—But Only…
Just when you thought it was safe to enjoy your weekend, the cybersecurity universe decided we needed another "4Shell" sequel. Grab your…

By Vinit Betkar
3 min read
Java4Shell (CVE-2026-114938): The Pre-Auth RCE That Wants to Break Your Enterprise Stack—But Only on Fancy CPUs
Just when you thought it was safe to enjoy your weekend, the cybersecurity universe decided we needed another "4Shell" sequel. Grab your coffee (and maybe some antacids), because we've got a new cinematic catastrophe on our hands: Java4Shell (CVE-2026-114938).
The tagline? This time, it's hardware-dependent.
Let's unpack what has security teams scrambling, why your CPU gets a vote, and how to stop the chaos.
What is Java4Shell? (Or: "The '=' That Broke the Internet")
Disclosed by security research firm Calif, Java4Shell targets a highly optimized version of Java's Base64 decoder.
Our servers spend their lives decoding Base64 strings—SAML artifacts, CSRF tokens, and HTTP Basic login headers. Since this happens millions of times a day, Java's compilers use high-performance code to speed things up.
But if an attacker sends a malformed string that ends with an extra =, this speed-demon decoder gets confused. It writes 62 or 63 bytes past the end of its intended output buffer.
By manipulating the server's memory (an attack method researchers affectionately named JavaBleed), attackers can expand a neighboring array, write bytes of their choosing, read your server's memory, and—finally—execute unauthorized code.
All without ever needing a valid login. It's the ultimate uninvited guest.
The Hardware Plot Twist: "Are You x86-64 Enough?"
Here is where the comedy/tragedy begins: Java4Shell is incredibly picky about its hardware.
This super-fast Base64 decoder is so optimized that it only runs on x86-64 Intel and AMD chips that support AVX-512 VBMI.
On the VIP list: Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids, and AMD Zen 4 or newer.
Absolutely Not Invited: ARM64 (like AWS Graviton) doesn't support those instructions, leaving them completely unaffected.
This creates the bizarre scenario where a Docker container running on a modern Intel server is vulnerable, but the exact same container running on ARM is totally fine.
If you are running Linux, you can run this command to see if your CPU is on Java4Shell's hit list (if it outputs all four flags, the hardware is vulnerable):
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
The Blast Radius: Who's in Trouble?
Because Base64 decoding often happens before authentication checks, Java4Shell gets past the front door without knocking. According to researchers, the vulnerability can be exploited without a login on the default settings of:
🔒 Atlassian Jira & Confluence
🛠️ Keycloak
🏗️ Jenkins
📦 JFrog Artifactory
🎟️ PingFederate
It also affects Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker if the attacker has at least a low-privilege login.
Who's affected?
Java 17 (17.0.6 and later)
Java 21, 25, and 27
(Standard Java 8 and 11 are safe, but specialized performance packs like 8u511b33-perf are affected).
The "Please Make it Stop" Playbook
Fortunately, you don't have to sit there waiting for the worst to happen. Here's how you can show Java4Shell the exit:
- The Right Way: Patch It Up
Oracle and the OpenJDK project have already released fixes. You want to update to the new .1 releases as soon as you can:
Java 17: Update to 17.0.21.1
Java 21: Update to 21.0.13.1
Java 25 & 27: Update to 25.0.5.1 and 27.0.1.1
Amazon Corretto and Azul Zulu also have patched builds ready. Remember: if you update container base images, you actually have to rebuild and redeploy them for the fix to apply!
- The Quick Workaround: The "Cool down, Java" JVM Flags
If you are waiting on a vendor's patch or can't reboot everything right away, you can disable the risky hardware acceleration entirely by starting your JVM with these flags:
-XX:-UseBASE64Intrinsics: This is the best fix. It turns off only the faster Base64 code, removing the vulnerable path while keeping your other AVX-512 speed optimizations.
-XX:UseAVX=2: This disables AVX-512 entirely. (Note: Only use this on x86-64 servers, because ARM64 machines will panic and refuse to start).
The Takeaway
Java4Shell is a fascinating reminder that cybersecurity doesn't end at the software layer. When a vulnerability exists at the intersection of a specific compiler optimization and CPU instruction sets, "Defense in Depth" really does have to go all the way down to the silicon.
Check your JVMs, run the Linux CPU check, and go get those .1 patches!
How is your team handling Java4Shell? Are your ARM servers laughing at your Intel ones? Let us know in the comments!