If your organisation runs Jira, Confluence, Jenkins or Keycloak, someone on your team should patch Java today. A critical bug called Java4Shell (CVE-2026-114938) lets attackers crash Java applications, read their memory and, in some cases, take over the server. Oracle released the fix on 17 November.
What makes the story bigger than one bug is how long it went unfixed. The flaw was first reported publicly in June, and a fix was proposed in September and then abandoned. It took an AI tool, an hour of work and less than US$200 to turn it into a working attack. It’s also the second time in a month that a core web technology has been exposed this way, after a leaked PHP bug put 1.3 million servers in the firing line in October.
What Java4Shell actually does
Base64 is a way of turning data into plain text, and it’s used everywhere: in login tokens, email attachments, web requests and security certificates. Java has a built-in Base64 decoder, and on newer Intel and AMD server chips it uses a faster, hardware-accelerated shortcut.
That shortcut has a memory bug. A specially crafted Base64 string makes the decoder write past the end of its memory space and overwrite nearby data before Java rejects the input. According to the researchers at Calif who built the working exploits, that can do three things:
- Crash the application. This is the easy part. A short burst of bad requests can reliably bring an affected service down.
- Leak memory. Attackers can read parts of the application’s memory, which may contain passwords, keys and login tokens.
- Run code on the server. This is the hard part. There’s no universal exploit, and each application needs its own tailored attack.
Who’s affected
You’re exposed only if all of these are true:
- You run an affected Java version. OpenJDK 17.0.6 and newer is affected, along with Java 21, 25 and 27, and distributions built from them such as Amazon Corretto, Eclipse Temurin, Azul Zulu, Red Hat and Microsoft’s builds. Standard Java 8 and Java 11 aren’t listed as affected, but Oracle’s Java 8 Enterprise Performance Pack is.
- It runs on a newer x86-64 processor with a feature called AVX-512 VBMI. That includes Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD EPYC and Ryzen from Zen 4 onwards. ARM processors, including Apple Silicon and AWS Graviton, are not affected.
- Your application decodes Base64 from untrusted input, such as data sent to a web service.
Calif showed attacks against popular enterprise software in its default setup:
- Before login: Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate.
- After login: Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker.
Calif says the list isn’t complete. It also demonstrated a client-side attack: a Java program that connects to a malicious server can be compromised too.
How serious is it really?
The scores differ. Oracle rates it 8.1 (High), noting that the attack is complex. Calif rates it 9.2 (Critical). The US Cybersecurity and Infrastructure Security Agency (CISA) has urged organisations to patch immediately.
For a sense of scale, the security firm OX Security estimates that about 0.8% of Java installations can be crashed remotely, and about 0.12% are realistic targets for a full takeover. Those are estimates based on assumptions, not measurements. And across the millions of Java servers worldwide, 0.12% is still a lot of servers.
As of 18 November, the threat intelligence firm GreyNoise had seen exploitation attempts but no confirmed successful attacks, according to Tenable. Calif hasn’t released its application-specific exploits yet, but at least two other security firms say they have built working ones.
The bug that waited five months
Calif’s disclosure timeline shows that the flaw wasn’t new:
- 9 June: a developer hit the bug in real use and filed a support issue with Adoptium, the group behind the Temurin Java builds.
- 8 to 9 September: a crash proof-of-concept was posted publicly, the root cause was identified, and a fix was proposed. The fix was closed without being merged.
- 24 October: Calif found the bug independently and reported it to Oracle with a working attack on Elasticsearch.
- 31 October: Calif sent Oracle working attacks on Jenkins and Keycloak that needed no login.
- 17 November: Oracle released the fix in its November Critical Patch Update.
For more than five months, a crash bug in one of the world’s most widely used runtimes sat in public view. It was treated as serious only once someone proved it could be used to take over servers. Calif says this “followed a pattern” it saw with PHP2Shell, the PHP flaw we reported in October, which also went public before a fix was ready and was rated 9.2. Java and PHP together run a large share of the world’s web servers, and both had critical flaws exposed within four weeks.
An hour of AI and less than US$200
According to Calif, researcher Quang Luong asked OpenAI’s Codex to audit the Java Virtual Machine. Codex found the bug in about an hour. Luong spent another two hours on the first working exploit. “The total token cost was less than $200,” Calif writes.
This is the bigger lesson of Java4Shell. Finding bugs like this used to take specialist skills and weeks of work. Now it takes an AI subscription and an afternoon, and attackers have access to the same tools. Unfixed bugs that sit in public bug trackers are now much easier to find and exploit.
It’s also a reminder that the biggest risks aren’t always attacks. Last week, Microsoft, the FAA and Chase all went down because of their own bugs and updates, with no hacker involved. Java4Shell is the other side of the same problem: a bug nobody fixed until an attacker could use it.
What to do now
1. Check your Java version. Run java -version on each server. Many products, including Jira, Confluence and Jenkins, can ship with their own bundled Java, which may differ from the system version. Check those too.
2. Check your processor (Linux). Run:
grep -o -w 'avx512f\|avx512bw\|avx512vbmi\|bmi2' /proc/cpuinfo | sort -u
If all four flags appear, your CPU uses the vulnerable code path.
3. Patch. Oracle’s fixed builds are:
| Version | Fixed build |
|---|---|
| Java 8 Enterprise Performance Pack | 8u513-perf |
| Java 17 | 17.0.21.1 |
| Java 21 | 21.0.13.1 |
| Java 25 | 25.0.5.1 |
| Java 27 | 27.0.1.1 |
If you use Corretto, Temurin, Zulu, Red Hat, Microsoft or another distribution, check that vendor’s advisory, because version numbers differ. The upstream advisory is on OpenJDK’s site.
4. If you can’t patch today, Calif lists two temporary workarounds, set when Java starts:
-XX:-UseBASE64Intrinsicsturns off the vulnerable shortcut. Keycloak recommends this as an interim fix.-XX:UseAVX=2turns off AVX-512 entirely. Use it only on x86-64 machines, because Java on ARM won’t start with it.
Oracle and OpenJDK don’t mention these flags in their advisories. Treat them as a stopgap, not a fix.
5. Prioritise internet-facing systems, especially anything with a login page that runs on Java: Jira, Confluence, Jenkins, Keycloak and single sign-on servers.
Why it matters here
Banks, mobile networks, government departments and software companies across Africa run the same tools Calif attacked: Jira and Confluence for project management, Jenkins for building software, and Keycloak for logins. Many of these systems are patched slowly, if at all. If you manage systems like these, assume someone is already scanning for them.
Zimbabwe’s telecoms regulator, POTRAZ, is developing a cybersecurity framework to protect critical infrastructure. Java4Shell is a real test of what that framework should require: who must patch, how fast, and who checks.
Related reading on TechBytes

