A Java4Shell flaw in OpenJDK allowed researchers to run code remotely on default installations of Jenkins, Jira, Confluence and Keycloak without signing in. Oracle released patches on November 17 for the vulnerability, which affects how certain Java runtimes process Base64 data on specific processors.
A shared Java component puts different applications at risk
Java applications use Base64 to handle encoded data in tasks such as authentication and file uploads. On some x86-64 processors, OpenJDK uses hardware acceleration to decode that data. Researchers at Calif found that the accelerated decoder could overwrite part of the Java process’s memory. Depending on the application, that corruption could expose sensitive information or allow an attacker to execute code.
The affected code dates back to OpenJDK 17.0.6. Several vendors incorporated it into their Java distributions, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK. Exposure depends on both the runtime and the processor. The vulnerable decoding function runs on x86-64 hardware that supports the AVX-512 VBMI instruction set.
Login requirements varied across the applications tested
Calif demonstrated remote code execution without credentials on six products. In addition to Jenkins, Jira, Confluence and Keycloak, the researchers reproduced that outcome on JFrog Artifactory and PingFederate. Their tests against Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker required an authenticated account.
Although the applications shared the same runtime flaw, each handled incoming data differently. The researchers had to establish how each product passed data to the affected decoder before they could demonstrate code execution. Calif published a demonstration of the underlying memory corruption and kept its application-specific exploits private.
Oracle patches the Java4Shell flaw
Oracle included the fix for CVE-2026-114938 in its November 17 security update and urged customers to apply the patches promptly. The company assigned the vulnerability a high severity score of 8.1 under CVSS 3.1. Calif used the newer CVSS 4.0 framework and rated it critical at 9.2.
For administrators who need time to deploy a patched runtime, Calif identified two temporary options. The more targeted workaround disables hardware-accelerated Base64 processing at startup with -XX:-UseBASE64Intrinsics. On x86-64 systems, -XX:UseAVX=2 disables AVX-512 instructions more broadly. Both options avoid the affected decoding function while administrators arrange the runtime update.


0 responses to “Java4Shell flaw exposes enterprise Java apps to attack”