Front pageVulnerabilities & Patches
Java4Shell: Critical Java Base64 Flaw Could Enable Remote Code Execution — Patch Now
Researchers say the bug in OpenJDK 17.0.6 and later can be used against apps such as Jenkins, Jira, Confluence and Keycloak; Oracle patched it on 17 November.
- Filed
- Read
- 4 min read
A newly disclosed vulnerability in OpenJDK, the open-source project behind many widely used Java distributions, could allow attackers to corrupt memory and potentially execute code remotely on vulnerable systems. Tracked as CVE-2026-114938 and nicknamed Java4Shell, the flaw affects the runtime’s hardware-accelerated Base64 decoder.
Security researchers at Calif disclosed the vulnerability on 17 November 2026, reporting that they had demonstrated remote code execution (RCE) against several widely deployed enterprise applications, including Jenkins, Atlassian Jira, Confluence and Keycloak.
The vulnerability is particularly concerning because it resides in the Java runtime rather than in one individual application. However, exploitation depends on specific processor capabilities, affected Java versions and whether attacker-controlled Base64 input reaches the vulnerable decoding routine.
Calif assigned the flaw a CVSS 4.0 score of 9.2 (Critical). The OpenJDK advisory lists a CVSS 3.1 score of 8.1 (High). These scores use different CVSS versions and should not be treated as directly interchangeable.
What the flaw does
Java4Shell originates in an optimised Base64 decoding routine within OpenJDK's HotSpot virtual machine. To accelerate decoding, the runtime uses specialised AVX-512 VBMI processor instructions on supported x86-64 hardware.
According to Calif's technical analysis, specially crafted Base64 input can trigger an integer-handling error in this accelerated routine. The decoder calculates an invalid output length, resulting in a heap buffer overflow that writes beyond the allocated memory buffer.
The immediate consequence is memory corruption. Depending on the surrounding application and memory layout, this could cause a Java process to crash, expose sensitive information held in memory or provide a route to remote code execution.
Calif demonstrated pre-authentication RCE in several applications running their default configurations:
- Keycloak
- Atlassian Jira
- Atlassian Confluence
- Jenkins
- JFrog Artifactory
- PingFederate
The researchers also reported post-authentication exploitation paths in applications including Apache Kafka, Apache Solr and Elasticsearch.
These demonstrations do not mean every installation of those products is automatically vulnerable. The affected Java runtime, processor architecture and application-specific execution path all matter. Calif also noted that there is no universal exploit that works identically against every application.
Which systems are affected?
The vulnerability affects OpenJDK-based Java runtimes, with the reported affected versions including Java 17 from version 17.0.6 onward, as well as the affected Java 21, 25 and 27 update branches.
Calif identifies several distributions that contain the affected OpenJDK code, including:
- Oracle Java SE and Oracle GraalVM
- Amazon Corretto
- Eclipse Temurin
- Microsoft Build of OpenJDK
- Azul Zulu
- BellSoft Liberica
- SAP SapMachine
- Red Hat OpenJDK
Oracle's affected build list includes:
- Oracle Java SE: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3
- Oracle GraalVM for JDK: 17.0.21.0.3 and 21.0.13.0.3
- Oracle GraalVM Enterprise Edition: 21.3.20.0.3
There are important exceptions. Standard Java 8 and Java 11 do not contain the affected Base64 decoding intrinsic; Oracle's Java 8 Performance Pack build is a specific affected exception.
Hardware requirements further narrow the exposure. The vulnerable decoding path requires an x86-64 processor supporting AVX-512 VBMI and the associated instruction capabilities. Calif identifies Intel Xeon processors from Ice Lake onward and AMD Zen 4 or newer processor families among the hardware that meets the requirements. ARM64 systems are not affected by this hardware-specific flaw.
A vulnerable Java version alone is therefore not enough to establish exposure. The application must also process attacker-controlled Base64 input through the affected decoder.
Patches and mitigation
Oracle released fixed Java builds as part of its 17 November security update. Organizations should identify the exact Java runtime used by their applications, including runtimes bundled inside products and container images.
Oracle's corresponding fixed releases include:
- Java 8 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
Other OpenJDK distributions maintain their own release schedules, so administrators should check the relevant vendor's security advisory rather than assume Oracle's build numbers apply to them.
Where an immediate update is not available, Calif recommends disabling the hardware-accelerated Base64 implementation with the JVM option:
-XX:-UseBASE64Intrinsics
Another suggested workaround, -XX:UseAVX=2, disables AVX-512 instructions and should only be applied to compatible x86-64 deployments. It must not be applied indiscriminately to ARM systems.
Organizations should prioritize internet-facing services, identity platforms and CI/CD infrastructure, while checking Java versions and CPU capabilities across servers, virtual machines and containers. Java applications that make outbound connections may also warrant attention, not just those exposing network services.
A vulnerability below the application layer
Java4Shell highlights the security implications of vulnerabilities in shared runtime components. A defect in a common decoding routine can affect multiple products that otherwise have different developers, deployment models and security controls.
For defenders, the challenge is not simply identifying whether an application uses Java. It is determining which runtime it actually executes, whether the underlying hardware enables the vulnerable code path and whether untrusted input can reach it.
With Oracle's fixes available and other vendors working through their own updates, organizations should treat runtime inventory and patch verification as immediate priorities.
Sources:
- Calif – Java4Shell technical research
- OpenJDK – Security advisory, 17 November 2026
- Oracle – November 2026 Critical Security Patch Update
- Red Hat – CVE-2026-114938 security advisory
- Equixly – Independent technical analysis
- Upwind – Java4Shell analysis and mitigation guidance
- The Hacker News – Java4Shell coverage
This brief was prepared with AI assistance from the sources above and reviewed by our editors.