OpenJDK Base64 Decoder Critical Memory Corruption ( CVE-2026-114938 )
A critical memory-corruption vulnerability in OpenJDK’s Base64 decoder, tracked as CVE-2026-114938 and nicknamed Java4Shell, may allow a remote attacker to corrupt JVM memory and potentially execute arbitrary code within an affected Java process. Java4Shell affects Java applications running on 64-bit x86 systems with AVX-512 VBMI support, where attacker-controlled Base64 input reaches the vulnerable Java decoder. Depending on the application’s implementation and input-processing flow, this can allow unauthenticated remote attackers to trigger memory corruption and potentially achieve remote code execution. Researchers have demonstrated pre-authentication remote code execution against default installations of Keycloak, Jira, Confluence, Jenkins, Artifactory, and PingFederate.
Oracle and OpenJDK released fixes on November 17, 2026 – patch affected Java deployments now. Oracle describes the flaw as difficult to exploit, with a CVSS 3.1 base score of 8.1.
Note: Java4Shell affects systems running on compatible 64-bit x86 (x86-64) processors with AVX-512 VBMI support. ARM64-based systems are not affected. Standard Java 8, Java 11 and Java 17.0.0-17.0.5 are also not affected.
NetSPI Product & Services Coverage
NetSPI EASM: NetSPI’s External Attack Surface Management has released version-based detection for CVE-2026-114938 (Java4Shell). Affected Java runtime versions will be identified and reported as Vulnerable Version – Java (CVE-2026-114938).
Because the exact Java runtime version and underlying CPU capabilities may not always be identifiable externally, NetSPI recommends that customers conduct an internal review of their Java-based applications and underlying runtime environments to assess potential exposure.
NetSPI Penetration Testing: NetSPI’s Penetration Testing Services can assist with verifying exposure and validating your patching efforts: NetSPI PTaaS.
Synack CVE Checks: Synack’s CVE catalog has been updated for crowd verification of exposure and patch validation.
Details
| CVE | CVE-2026-114938 | ||||
| Severity | Oracle scores it 8.1 (High) under CVSS 3.1, vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. According to Calif Research, the vulnerability has a CVSS 4.0 severity score of 9.2 (Critical). NVD scoring is pending. | ||||
| Attack Vector | Network. No credentials and no user interaction required. Oracle rates attack complexity as high. | ||||
| Root Cause | Heap-based Buffer Overflow (CWE-122): The optimized Base64 decoder in OpenJDK uses low-level CPU instructions to process input. When the input ends with padding characters (=), it may incorrectly calculate the output length, resulting in a negative value. This can cause the decoder to write a full 64-byte block beyond the allocated output buffer, corrupting adjacent memory. Although Java subsequently rejects the malformed input, the memory corruption has already occurred. However, successful exploitation depends on several factors, including the Java runtime version, processor capabilities, and whether an application exposes a reachable functionality that passes attacker-controlled Base64 input to the vulnerable decoder. | ||||
| Impact | – An unauthenticated remote attacker may be able to trigger heap memory corruption in vulnerable Java applications by supplying specially crafted Base64-encoded input – Successful exploitation may allow attackers to overwrite neighboring heap objects, potentially corrupting application data and JVM memory structures – Attackers may exploit memory corruption to disclose sensitive information – An attacker can combine the memory corruption with heap disclosure to achieve remote code execution within the vulnerable Java process | ||||
| Affected Products | Oracle Advisory (November 17, 2026): Oracle’s November 2026 Risk Matrix lists the following affected versions for CVE-2026-114938: – 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 OpenJDK Advisory (November 17, 2026): – Identifies CVE-2026-114938 as a HotSpot Compiler vulnerability – Affected JDK release lines: 17, 21, 25, and 27 Calif Research Disclosure (November 17, 2026): – Reports that OpenJDK 17.0.6 and newer versions may be affected – Identifies several Java distributions built from OpenJDK that may be affected, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle OpenJDK, Oracle Java SE, and Oracle GraalVM for JDK | ||||
| KEV Status | Not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog as of November 18, 2026. No exploitation in the wild has been reported; however, a public proof-of-concept that reproduces the memory corruption has been released. | ||||
Discovery & Remediation Guidance
- Review and Audit
- Identify all Java installations across production, staging, development, and testing environments.
- Record the Java vendor, full runtime version, and build information using
java -version. - Prioritize JDK 17, 21, 25, and 27 release lines and validate each installation against the applicable vendor advisory.
- Identify x86-64 hosts that support AVX-512 VBMI and the additional CPU flags required by the vulnerable execution path.
- Identify applications that process attacker-controlled Base64 data, particularly authentication workflows, API endpoints, file uploads, and network messaging functionality.
- Prioritize internet-facing applications and authentication services where Base64 decoding may occur before authentication.
- Review application, web server, authentication, and endpoint logs for suspicious requests, unexpected Java process behavior, or abnormal JVM crashes.
- On Linux, check
/proc/cpuinfofor these flags: avx512f, avx512bw, avx512vbmi, and bmi2. Hosts with all four may meet the CPU requirements for Java4Shell. Having the flags does not confirm that an application is exploitable. Exploitability also depends on whether the application decodes untrusted Base64 input through an affected JDK.
- Patch Immediately
- For Oracle Java SE and GraalVM, follow Oracle’s November 2026 Critical Patch Update and confirm the installed build includes the fix.
- For OpenJDK-based distributions, follow the respective vendor’s security advisory and update guidance (OpenJDK).
- Update Java runtimes bundled within applications, containers, and appliances through the supported vendor process.
- Restart affected Java services as required and verify that the updated runtime is in use.
Note: Consider the following options as temporary risk-reduction measures. They are not a replacement for applying the vendor-provided security update. Both are JVM startup flags and take effect only after the Java process is restarted.
- Mitigation (If Patching Is Delayed)
- Add
-XX:-UseBASE64Intrinsicsto the JVM startup options. This disables hardware-accelerated Base64 encoding and decoding. - Add
-XX:UseAVX=2to disable AVX-512 usage by the JVM. Apply this option only on x86-64 systems. OpenJDK on ARM does not recognize this option and may fail to start.
- Add
NetSPI Internal Response
NetSPI and Synack found a potential vulnerability to CVE-2026-114938 and have implemented mitigations accordingly. Continuous review, monitoring, and patch validation remain in place.
Additional Resources
Explore More Blog Posts
The Attack Path Problem: How Complexity Hides Risk in Financial Services
If you work in financial services, you know the scale of findings isn’t the hardest part. How the findings connect is what really matters. Learn how to pressure-test your security approach against modern AI attacks to your actual environment.
Apache HTTP Server: Critical RCE Vulnerability ( CVE-2026-119618 )
The Apache Software Foundation has disclosed a critical vulnerability, CVE-2026-119618, in the HTTP/2 module (mod_http2) of Apache HTTP Server.
You’ve Got (Graph) Mail – Leveraging Microsoft Graph API Change Notifications for Data Exfiltration
Discover how threat actors leverage Microsoft Graph API Change Notifications and Rich Notifications for stealthy post-exploitation data exfiltration of Outlook emails and Teams messages.