Java4Shell CVE-2026-114938: Patch OpenJDK RCE Flaw

U.S. cybersecurity authorities are urging organizations to patch CVE-2026-114938, a high-severity OpenJDK vulnerability dubbed “Java4Shell” that can enable unauthenticated remote code execution in vulnerable Java applications. The flaw carries a CVSS v3.1 score of 8.1 and affects an optimized Base64-decoding path in the HotSpot JVM. NIST’s NVD record and the EU Agency for Cybersecurity’s advisory describe the issue as a memory-corruption vulnerability that can cause denial of service and, under certain conditions, code execution. [5][18]

The vulnerability is triggered when a Java process decodes specially crafted Base64 input. The affected fast path is used on x86-64 systems exposing AVX-512 Vector Byte Manipulation Instructions, or VBMI, meaning the risk is concentrated in supported servers and workstations rather than every Java deployment. ARM64 systems are not affected, and exploitation also requires an application to pass attacker-controlled data to the vulnerable decoder. The Canadian Centre for Cyber Security says successful exploitation could result in memory corruption, process crashes, sensitive-data disclosure or arbitrary code execution. [6]

OpenJDK releases from 17.0.6 onward are affected when the vulnerable hardware-accelerated path is available, with the issue also impacting Java 21, 25 and 27 builds before their respective fixes. Oracle’s affected product list includes Java SE performance builds, Oracle GraalVM for JDK and Oracle GraalVM Enterprise Edition. Security fixes released November 17 include OpenJDK 17.0.21.1, Java 21.0.13.1, Java 25.0.5.1, Java 27.0.1.1 and Java SE 8u513 for the affected performance build. [18]

The disclosure has prompted warnings from CISA and other national cybersecurity agencies, but CVE-2026-114938 was not listed in CISA’s Known Exploited Vulnerabilities catalog as of November 18. Public technical details and trigger code have nevertheless accelerated testing by defenders and researchers. Security firms reported reproducing crashes and memory corruption in laboratory environments, while public reporting had not established confirmed exploitation in the wild at the time of publication. [16][17][27]

Organizations should inventory Java runtimes on x86-64 systems, identify services that decode Base64 data from untrusted users or network clients, and apply the appropriate vendor or distribution update without waiting for evidence of active attacks. Where immediate patching is impractical, defenders should assess whether the vulnerable Base64 intrinsic can be disabled as a temporary mitigation, while recognizing that configuration changes can affect performance and must be validated. Administrators should also monitor internet-facing Java services for crashes, unusual requests and other signs of attempted exploitation.

References

  1. NVD-CVE-2026-114938 – NIST
  2. AL26-029 – Critical vulnerability impacting Oracle Java – CVE-2026-114938 – Canadian Centre for Cyber Security
  3. Java4Shell (CVE-2026-114938): affected versions and fixes
  4. Security Advisory 2026-021
  5. OpenJDK RCE Vulnerability (Java4Shell)
  6. Java4Shell (CVE-2026-114938) | Mallory

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply