Java4Shell is fixed upstream, but your Linux packages may not be yet. Here's the stopgap
A serious Java bug called Java4Shell was published last night, and the advice everywhere is "patch now". The catch, if your Java came from your Linux distribution, is that there may not be a patch in your package manager yet.
So this post is about the gap. How to tell if you're exposed, and what to put in place until apt or dnf has something to give you.
What happened
The bug is CVE-2026-114938. It's in the part of Java that decodes Base64, a way of turning data into plain text that web apps use all over the place. The researchers at Calif, who also found PHP2Shell, published the details on 17 November, the same day Oracle and the OpenJDK project released fixes.
Their write-up says "a remote attacker with no credentials can overwrite heap memory". In plain English: send the right text to the right app and you can crash it, or in some cases take it over. CISA has told organisations to "immediately patch". Talos says it "has not observed in-the-wild exploitation" yet, and The Register has a good overview.
Dev Partners covered what it means if your app runs on Java this morning, including how to find every Java process on a box. I'm looking at the server underneath.
Does it affect you?
Three things have to line up.
Java 17.0.6 or newer. That's Java 17, 21 and 25, from any supplier. Calif lists Temurin, Corretto, Zulu, Red Hat's builds and Oracle's own, because they're all built from OpenJDK.
The right kind of processor. The bug only bites on x86-64 chips with a feature called AVX-512 VBMI. Calif names Intel Xeon from Ice Lake onwards and AMD Zen 4 or newer. ARM servers aren't affected. Check with:
grep -o avx512vbmi /proc/cpuinfo | head -1No output means this machine is fine. Run it on cloud servers too, as you don't always know which chip you've been given.
An app that decodes Base64 from outsiders. Calif showed attacks needing no login against default setups of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. That list isn't complete, and plenty of in-house apps decode Base64 too.
Where the Linux fixes are
When I checked this morning, the Debian security tracker had fixed versions only in unstable. The openjdk-17, openjdk-21 and openjdk-25 packages in Debian 12 and 13 were still marked vulnerable.
Red Hat says it "is investigating which shipped OpenJDK builds" are affected, and lists no fixed packages yet. I couldn't find an Ubuntu security notice for it either.
That will change. But "patch now" doesn't help much if there's nothing to install.
What to do this week
1. Find out what Java you've got and where it came from. On Debian or Ubuntu, dpkg -l 'openjdk-*' lists the packaged ones. On Red Hat, Alma or Rocky, rpm -qa | grep -i openjdk. Then remember that Jira, Confluence and lots of Docker images bring their own Java, which your package manager won't touch.
2. Put the stopgap in now. Calif gives two JVM options. The one I'd use is -XX:-UseBASE64Intrinsics, which switches off just the fast Base64 code where the bug lives. The other, -XX:UseAVX=2, turns off AVX-512 altogether, and Calif warns that Java on ARM "will fail to start" with it. Either may cost a little speed.
The tidy way to apply it to a service is a systemd override. This is my suggestion rather than the researchers'. Run sudo systemctl edit jenkins (or whatever the service is called) and add:
[Service]
Environment="JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics"Restart the service and check its log for a line starting Picked up JAVA_TOOL_OPTIONS. That's Java telling you it took the setting. If the service already sets JAVA_TOOL_OPTIONS, add the flag to what's there rather than replacing it.
For Docker, set the same variable in the environment: section of your compose file and recreate the container.
3. Patch as soon as the packages land. Run your normal updates every day this week. When the new OpenJDK arrives, restart every Java service. A running Java process keeps using the old code until it's restarted, and unattended upgrades won't do that for you.
4. Don't forget the bundled ones. For Jira, Keycloak and friends, watch the vendor's advisory. For Docker, rebuild on a fixed base image once there is one.
5. Take the stopgap out later. Once you're patched, remove the override and restart. Write yourself a note now, or it'll still be there in three years with nobody sure why.
The bigger point
The fix came out yesterday and the attack details are already public, so the gap between the two is the risk. Dev Partners wrote yesterday about AI turning security patches into working attacks, and Calif say they used AI to find this bug and build the first exploit, for "less than $200" in AI costs. That gap is only getting shorter.
If a bespoke Java app runs your business and nobody's sure what it does with Base64, the team at Dev Partners look after existing software and can find out.
And if you'd rather someone else watched the Debian tracker and did the restarts, that's what my support retainers are for.
Liked that? Get the next one by email
When a security flaw lands that could affect your server, I'll email you what it means and what to do. Plus the odd opinion piece. Not often, no spam.