Several cyber agencies, including the Centre for Cybersecurity Belgium (CCB), are urging organisations to patch the critical Java vulnerability Java4Shell as a top priority. On recent Intel and AMD processors, the flaw can give attackers unauthenticated access to Java applications.
The US cybersecurity agency CISA is also calling for immediate patching. The flaw, tracked as CVE-2026-114938, sits in the Base64 decoder of the HotSpot Java Virtual Machine (JVM) for x86-64. Oracle, which owns Java, gives it a CVSS score of 8.1.
According to the CCB, a very large share of server software runs on Java, from identity platforms to build servers and search engines. Because Java is often bundled with third-party products, container images and appliances, organisations may be running affected versions without knowing it.
Last month, a flaw in the PHP software made plenty of headlines, with large companies taking their websites offline as a precaution. PHP is an open source language that large parts of the internet run on. Java is also one of the best-known programming languages.
Which systems are at risk from Java4Shell?
An attack only works if three conditions are met at the same time: an x86-64 processor with AVX-512 VBMI, an affected Java build, and an application that passes attacker-controlled data to the Base64 decoder. Affected processors include Intel Xeon from Ice Lake to Granite Rapids, AMD EPYC and Ryzen from Zen 4 onwards, and Intel PC processors from 2019 to 2021. ARM64 processors are not affected.
The flaw affects OpenJDK from version 17.0.6 onwards and derived distributions such as Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK. Security company Calif, which discovered the flaw, showed that attackers can execute code without logging in in products such as Keycloak, Jira, Confluence, Jenkins and PingFederate. Those products are not vulnerable themselves. They are at risk when they run on an affected Java build. According to the CCB, workstations are also at risk, because a Java program that connects to a malicious TLS server can be compromised as well.
Patch and renew keys
Oracle fixes the flaw in its Critical Patch Update of November 2026. The CCB advises organisations to track down every Java runtime in their environment, install each vendor’s patched build and restart every JVM. A Java update from the operating system does not always cover bundled runtimes, and not every distribution has a patched version yet. Organisations that cannot update right away can, after thorough testing, use temporary JVM settings that disable the affected code path.
Internet-facing Java applications that ran on an affected build and affected hardware may have exposed secrets from their memory. The CCB therefore advises renewing keys, tokens and credentials and investigating repeated crashes of Java applications. A patch does not undo an earlier breach. Incidents can be reported via ccb.belgium.be.
