Java4Shell: Why Your Jenkins, Jira or Confluence Server Needs Attention Today
By Zachary, Hawthorn Security
Most of my posts are about PHP, WordPress and Node, because that's what most small businesses run. But plenty of small dev teams also have a Java app or two quietly running in the corner: a Jenkins server that builds and deploys the website, a self-hosted Jira or Confluence, or a Keycloak login server. Those boxes tend to get set up once and then forgotten.
On Tuesday evening a serious Java flaw went public. It's been nicknamed “Java4Shell”, and if you run any of those tools yourself, it's worth a few minutes of your time today.
What happened
On 17 November 2026, at around 9pm UK time, the security firm Calif disclosed CVE-2026-114938, a bug in OpenJDK. OpenJDK is the open-source engine underneath nearly every Java install. Oracle released its monthly Java patches at the same time.
The bug is in the code Java uses to decode Base64. Base64 is a very common way of packing data into text, used for things like login headers and file uploads. On some modern processors, Java switches to a fast, hardware-accelerated version of that code. If an attacker sends carefully malformed data, that fast version writes past the end of its memory buffer. Java does reject the bad input afterwards, but by then the damage is done. Calif says this can be used to leak memory and, with effort, to run the attacker's own code on your server.
It has been rated 9.2 out of 10 (critical) on the CVSS 4.0 scale.
Who's affected
There are three conditions:
- Java version. Calif says OpenJDK 17.0.6 and later are affected. That includes Java 21, 25 and 27, plus the popular builds made from OpenJDK, such as Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft's build, Red Hat's build and Oracle Java itself.
- The processor. The vulnerable code only runs on x86-64 chips with a feature called AVX-512 VBMI. That means recent Intel Xeon chips (Ice Lake and newer) and AMD EPYC or Ryzen chips from Zen 4 onwards. Plenty of modern cloud servers and VPSs run on exactly these chips. ARM servers are not affected.
- Exposure. The attacker needs to get data to your Java app. In Calif's testing, normal features like logging in or uploading a file were enough.
Products where Calif says it got code running without logging in include Jenkins, Atlassian Jira, Atlassian Confluence, Keycloak, JFrog Artifactory and PingFederate. Calif also got code running after logging in on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. Calif is clear that the list isn't complete. Calif also says a Java program that simply connects out to a malicious server over TLS can be hit, even if it doesn't accept any connections itself.
How worried should you be?
Being measured about it: as of 17 November, nobody had reported this being exploited in the wild. Calif says there's no one-size-fits-all exploit, as each target needs its own work. It's also holding back its product-specific attack details until people have had time to patch.
That said, Wiz reports its AI research tool produced a working proof of concept in about two hours. History tells us attackers move quickly on bugs like this. “No known attacks yet” is a window to use, not a reason to wait.
The traps people miss
- Your Linux distro may not have a fix yet. At the time of writing, Debian marked all its releases as vulnerable with no fix out, Ubuntu's latest openjdk-17 and openjdk-21 packages were the last affected builds, and Red Hat said fixes were being expedited. Running
apt upgradetoday may not actually fix this. Check the package changelog mentions the CVE. - Temurin had no confirmed fix yet when I checked. If you use Temurin (very common in Docker images), keep an eye on Adoptium's releases.
- Bundled Java. Many apps ship their own copy of Java rather than using the system one. Updating the server's Java package won't touch those.
- Containers need rebuilding. If your Jenkins or Keycloak runs in Docker, the Java inside the image only changes when you pull or rebuild a patched image.
- The forgotten VPS. The Jenkins box someone set up three years ago, open to the internet “just for webhooks”, is precisely the target here.
What you should do
- Find your Java. List anything running Java on your servers (
ps -C java -o pid,cmdon Linux), including inside containers, and note the version. - Check the processor. On Linux, run:
grep -oE '(avx512f|avx512bw|avx512vbmi|bmi2)' /proc/cpuinfo | sort -u. If all four come back, the vulnerable code path is in play. - Patch where you can. Oracle's fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Amazon Corretto's fixed builds are 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4. For distro packages and Temurin, install the fix as soon as it lands, then confirm the version really changed.
- Use the stopgap if you can't patch yet. Calif's recommended workaround is to start Java with
-XX:-UseBASE64Intrinsics, which turns off the fast code path. You can usually set it through theJAVA_TOOL_OPTIONSenvironment variable, then restart the app. There may be a small performance cost. - Get these tools off the open internet. Jenkins, Jira, Confluence and Keycloak admin pages rarely need to be public. Put them behind a VPN, an IP allow-list or a login proxy. That's good practice regardless of this bug.
- Rebuild your containers once fixed base images are available, and redeploy them.
- Update the rest of your Java too. Oracle's November update also fixes other flaws, including in Java 8 and 11, so don't skip those versions just because this particular bug may not apply.
Not sure what's running on your servers?
This is the sort of thing I see a lot: a business that's careful with its website but has a build server or internal wiki nobody has looked at in years. A Hawthorn Security review goes through your servers, VPSs, containers and deployment pipeline, finds what's exposed and out of date, and gives you a plain-English list of what to fix first.
Book a security review at hawthornsecurity.uk
Sources
- Calif: Java4Shell, RCE in OpenJDK when processing Base64
- Wiz: CVE-2026-114938 OpenJDK RCE (Java4Shell)
- Censys: Nov 17 Advisory, OpenJDK Remote Code Execution
- Aikido: Java4Shell pre-auth RCE in Java 17
- ComputingForGeeks: Java4Shell, patch vulnerable OpenJDK
- The Hacker News: Oracle to patch 11 Java flaws
- Rapid7: CVE-2026-114938