November 18, 2026
Java4Shell: Understanding CVE-2026–114938 in OpenJDK
A new critical vulnerability, CVE-2026–114938, has been identified in OpenJDK’s optimized Base64 decoder. With a CVSS 4.0 score of 9.2…

By Tanmay Shelke
1 min read
A new critical vulnerability, CVE-2026–114938, has been identified in OpenJDK's optimized Base64 decoder. With a CVSS 4.0 score of 9.2 (Critical), the vulnerability could potentially lead to memory corruption, denial of service (DoS), and, under the right conditions, remote code execution (RCE). [securityla…adoghq.com]
What is CVE-2026–114938?
The vulnerability is an out-of-bounds memory write in OpenJDK's optimized Base64 decoding implementation.
Specially crafted malformed Base64 input can cause an incorrect output-size calculation. On affected systems, the optimized AVX-512 decoding routine may consequently write beyond the allocated Java array and corrupt neighboring JVM memory. [securityla…adoghq.com]
Although RCE is theoretically possible, Datadog Security Labs notes that denial of service is easier to achieve, while reliable RCE requires exploitation tailored to the specific application and JVM environment. There is no universal exploit that automatically works against every Java application. [securityla…adoghq.com]
Who is affected?
According to the published analysis, vulnerable releases include: [securityla…adoghq.com]
- Java 17: 17.0.6 through versions before 17.0.21.1
- Java 21: versions before 21.0.13.1
- Java 25: versions before 25.0.5.1
- Java 27: versions before 27.0.1.1
Importantly, exploitation also requires an x86–64 CPU supporting AVX-512 VBMI and an application path that sends attacker-controlled input into the vulnerable Base64 decoder. Native ARM64 Java runtimes are not affected by this specific issue. [securityla…adoghq.com]
How to mitigate it
The recommended solution is straightforward: upgrade the Java runtime to a fixed release, including Java runtimes bundled inside applications and container images. Affected Java processes should then be restarted. [securityla…adoghq.com]
If immediate patching isn't possible, Datadog Security Labs reports that disabling Base64 intrinsics using
-XX:-UseBASE64Intrinsics-XX:-UseBASE64Intrinsicsprevented the out-of-bounds writes in its testing. On affected x86–64 environments, restricting the JVM to AVX2 using -XX:UseAVX=2 is another temporary option, although it may have broader performance implications. [securityla...adoghq.com].
Final Thoughts
Java4Shell is serious, but exposure is highly environment-dependent. Security teams should prioritize identifying vulnerable Java versions, checking CPU support for AVX-512 VBMI, determining whether untrusted input reaches Java's affected Base64 decoder, and patching exposed systems as soon as possible. [securityla…adoghq.com]
Reference: Java4Shell: Remote Code Execution in OpenJDK (CVE-2026–114938) | Datadog Security Labs [securityla…adoghq.com]
Thanks for reading — more cybersecurity and vulnerability research write-ups coming soon 🔐