A high-risk Java security vulnerability, which is also known as Java4Shell (CVE-2026-114938), has questioned the security of all corporate business servers and the connected applications running affected OpenJDK builds.
Since November 17 till now, it has been disclosed that this severe flaw affected an optimised Base64 decoding implementation in the OpenJDK HotSpot JVM and it could allow remote code execution in some conditions.
All affected organisations are being advised to identify the Java runtimes and vulnerable systems. Then, they can apply the important security updates.
About Java4Shell Vulnerability
Java4Shell is basically a memory-corruption flaw in the JVM’s Base64, which decodes functionality.
The vulnerability involves memory corruption in the JVM’s optimised Base64 decoder. Specially crafted input can trigger an out-of-bounds memory write, potentially resulting in application crashes, sensitive information disclosure, or remote code execution.
The vulnerability has two reported severity scores:
- Oracle: 8.1 under CVSS 3.1 (High).
- Calif researchers: 9.2 under CVSS 4.0 (Critical).
These scores use different CVSS versions and should be understood separately.
Which Java Builds Are Affected?
Java4Shell (CVE-2026-114938) affects specific OpenJDK release lines and Oracle Java builds. According to the security advisory, the affected builds are:
| Java Product | Affected Builds |
| Oracle Java SE 8 | 8u511b33-perf |
| Oracle Java SE 17 | 17.0.21.0.3 |
| Oracle Java SE 21 | 21.0.13.0.3 |
| Oracle Java SE 25 | 25.0.5.0.3 |
| Oracle Java SE 27 | 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 |
The vulnerability also affects the OpenJDK 17, 21, 25, and 27 release lines. Exploitation requires an x86-64 processor supporting AVX-512 VBMI and the vulnerable Base64 decoding code path.
Note: Standard Java 8 and Java 11 are not affected by this vulnerability. The Java 8 performance build is a specific exception. Organisations should check their Java distribution’s advisory rather than relying on version numbers alone.
All Security Fixes
The fixed versions till now include:
| Java Release | Fixed Version |
| Java 17 | 17.0.21.1 |
| Java 21 | 21.0.13.1 |
| Java 25 | 25.0.5.1 |
| Java 27 | 27.0.1.1 |
Users of Amazon Corretto, Eclipse Temurin, and other Java distributions should check with their vendors for corresponding patches.
How Can Organisations Protect Their Systems?
Organisations should:
- Identify Java installations linked to all servers, applications, and containers.
- Check whether processors support AVX-512 VBMI.
- Install the relevant security updates.
- Review third-party applications that bundle their own Java runtimes.
Administrators can disable the affected Base64 intrinsics using the JVM option:
-XX:-UseBASE64Intrinsics as a temporary mitigation.
This disables the affected hardware-accelerated Base64 implementation and is a temporary workaround, not a replacement for patching. This should be tested before deployment and does not replace installing the security patch.
How to check CPU compatibility?
Linux administrators can check CPU flags using:
| grep -m1 ‘^flags’ /proc/cpuinfo | tr ‘ ‘ ‘\n’ | grep -E ‘^(avx512f|avx512bw|avx512vbmi|bmi2)$’ |
The relevant CPU flags help administrators identify potentially affected hardware.
Is Java4Shell Being Exploited?
As of November 18, public reporting had not established widespread real-world exploitation. However, the availability of proof-of-concept code increases the urgency of identifying and patching vulnerable deployments.
But it doesn’t mean that the proof-of-concept availability does not establish widespread real-world exploitation. Organisations should nevertheless prioritise patching and monitoring affected systems.
Java4Shell highlights the importance of checking not just Java versions but also processor compatibility and bundled runtimes when assessing infrastructure security.




