If you've got anything running on Java, and that includes off-the-shelf tools like Jira, Confluence, Jenkins or Keycloak as well as your own Spring Boot apps, there's an update you want on this week's list. Yesterday (17 November) Oracle and the OpenJDK project released fixes for a bug in Java's Base64 decoder. It's been given CVE-2026-114938 and a CVSS 4.0 score of 9.2, which is rated critical.
The researchers who found it, Calif, have called it Java4Shell. That's the same team behind PHP2Shell, which I wrote about earlier this month. So if that name rings a bell, that's why.
What the bug actually is
Base64 is everywhere. It's how a lot of data gets squeezed into text: login headers, tokens, email attachments, bits of SAML when you sign in with single sign-on. Java has a built-in decoder for it, java.util.Base64, and almost everything uses it.
To make that decoder fast, the Java runtime (HotSpot) has a hand-optimised version that uses AVX-512 instructions on modern x86-64 processors. According to Calif's write-up, that fast path gets its sums wrong when the input ends in padding (the = characters on the end). It writes more bytes than it should, past the end of the buffer. Java then rejects the input as invalid, but by then the damage to memory has already been done.
Calif says that's enough to overwrite memory, read memory it shouldn't, and in the right conditions run code on the server. CISA's alert says the flaw "could crash the JVM and allow for unauthenticated remote code execution".
Who is affected
This is the part worth reading carefully, because it's narrower than "all Java everywhere", but not by as much as you'd hope.
- Java version: Talos and Calif both say OpenJDK 17.0.6 and later. That covers Java 17, 21 and 25, which is most modern Java.
- Every major build: Calif lists the builds that inherit the bug, including Eclipse Temurin, Amazon Corretto, Azul Zulu, Red Hat's OpenJDK, Microsoft's build and Oracle's own Java SE. Changing vendor doesn't get you out of it.
- The processor: it only bites on x86-64 CPUs with AVX-512 VBMI. Calif names Intel Xeon from Ice Lake onwards and AMD Zen 4 or newer. Calif says ARM64 isn't affected.
- The app: the attacker needs to get their Base64 into your app's decoder, and the code has to be busy enough for Java to have compiled the fast path. On a web app, that's not a high bar.
Calif tested a list of well-known Java products. It reports remote code execution without logging in against default setups of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate, and after logging in against Kafka, Solr, Elasticsearch and others. It also built working attacks on sample apps written with Spring Boot and Apache Struts. That last one matters if you've had custom software built in Java, because those are two of the most common ways to build it.
There is some good news. Talos says it "has not observed in-the-wild exploitation of this vulnerability yet." And Calif points out that "There is no universal payload": each target needs its own exploit worked out. That slows attackers down a bit. It doesn't stop them. Calif says it found the bug and built the first exploit with AI help for less than $200 in tokens, which is the same story I covered in AI can now turn a security patch into an attack. Once the patch is public, the clock is running.
How to check your own servers
Two quick checks on each Linux server.
First, does the CPU have the feature? Run grep -o avx512vbmi /proc/cpuinfo | head -1. If it prints nothing, this particular bug can't be reached on that machine. If it prints avx512vbmi, carry on. Don't assume a cloud server is too old or too new to matter. Check.
Second, which Java is actually running? java -version tells you about the one on the path, but that's often not the one doing the work. Tools like Jira and Confluence usually ship with their own bundled Java, Docker images bring their own, and plenty of apps are started with a full path to a JDK somewhere under /opt. ps aux | grep java shows you the real binaries in use, and you can run each one with -version.
What to do about it
Update. That's the main answer, and CISA's wording is "CISA strongly urges organizations to immediately patch". In practice that means:
- System packages: pull the patched OpenJDK from your distribution or vendor and restart every Java process. A Java app keeps running the old runtime until it's restarted.
- Containers: rebuild your images on an updated base image and redeploy. Pulling the same tag next month isn't a plan.
- Bundled Java: for products like Jira, Confluence or Jenkins, follow the vendor's own advisory, because they may need a product update rather than a system one.
Check your vendor's release notes for the exact fixed version numbers for 17, 21 and 25 rather than trusting a blog post (this one included).
If you can't patch straight away, Calif gives two stopgaps. Starting the JVM with -XX:-UseBASE64Intrinsics switches off the fast Base64 path. Or -XX:UseAVX=2 switches off AVX-512 altogether, which Talos also recommends. Calif warns that the UseAVX flag is for x86-64 only and an ARM JVM won't start with it, so don't paste it into a shared config that runs on both. Either flag may cost a little speed. That's a fair trade for a week.
The real question: who would have noticed?
Patching is the easy bit. The hard bit is knowing this applies to you. Java tends to hide. It's inside the build server nobody's logged into for a year, the single sign-on box someone set up and moved on from, or the reporting tool that came with a contract. If nobody owns those servers, nobody reads the CISA alert on a Tuesday night.
If you'd like a second pair of eyes, our code audit (£250 + VAT) looks at one app along with its server and database, including whether it's patched and what it depends on. If you'd rather someone just kept on top of it, Look after it (from £355 a month + VAT) covers keeping your software's runtime, frameworks and hosting up to date and watched. On the pure server side, I also do server health checks and monthly server retainers.
In the meantime, run those two checks today. They take a couple of minutes. If you find Java somewhere you didn't expect and you'd like a hand, get in touch.
Cheers, Rob

