Oracle Java SE and GraalVM Heap Buffer Overflow: CVE-2026-114938 #
Oracle and OpenJDK disclosed that certain versions of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, and OpenJDK, including distributions built from OpenJDK (Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, and Oracle OpenJDK), are affected by a heap-based buffer overflow in the HotSpot compiler. A flaw in the optimized x86-64 Base64 decoder causes malformed input to write past the end of an allocated array. An unauthenticated, remote attacker who can supply data to an application that decodes Base64 content can trigger this out-of-bounds heap write. Depending on the application and heap layout, the write may lead to adjacent memory reads, denial of service, or remote code execution (RCE). This vulnerability has been designated CVE-2026-114938, rated high with a CVSS score of 8.1, and publicly disclosed under the name "Java4Shell."
Researchers demonstrated that the write can be turned into heap memory disclosure and RCE through the vulnerable Base64 decoder in default configurations of several Java applications, including Jenkins, Atlassian Jira and Confluence, JFrog Artifactory, Keycloak, Apache Solr, Elasticsearch, and Gerrit. Incorrect heap placement can crash the JVM. Instances of these applications running on an affected Java runtime are exposed.
The following versions are affected
- Oracle Java SE 8: Version 8u511b33-perf
- Oracle Java SE and OpenJDK 17: Versions 17.0.6 through 17.0.21.0.3
- Oracle Java SE and OpenJDK 21: Versions through 21.0.13.0.3
- Oracle Java SE and OpenJDK 25: Versions through 25.0.5.0.3
- Oracle Java SE and OpenJDK 27: Versions through 27.0.1.0.3
- Oracle GraalVM for JDK 17: Version 17.0.21.0.3
- Oracle GraalVM for JDK 21: Version 21.0.13.0.3
- Oracle GraalVM Enterprise Edition 21.3: Version 21.3.20.0.3
What is Java SE and OpenJDK? #
Java SE and OpenJDK are widely deployed Java runtimes and development kits used to run server, desktop, and embedded applications. Oracle GraalVM is a high-performance JDK distribution built on the same Java platform.
What is the impact? #
Successful exploitation of this vulnerability would allow an unauthenticated, remote attacker to disrupt service availability, expose sensitive application data, or potentially gain complete control of affected systems.
Are any updates or workarounds available? #
Users are encouraged to update to the latest version as quickly as possible:
- Oracle Java SE 8 and Oracle Java SE and OpenJDK 17, 21, 25, and 27: Upgrade to the release containing the November 2026 Critical Security Patch Update fix from your Java vendor.
- Oracle GraalVM for JDK 17 and 21: Apply the November 2026 Critical Security Patch Update.
- Oracle GraalVM Enterprise Edition 21.3: Apply the November 2026 Critical Security Patch Update.
Mitigation:
Either of the following options mitigates the vulnerability; applying both is not required.
- Start the Java runtime with "-XX:-UseBASE64Intrinsics" to disable hardware-accelerated Base64 encoding and decoding.
- Start the Java runtime with "-XX:UseAVX=2" to disable AVX-512. Apply this flag only on x86-64 hosts, as OpenJDK on ARM does not recognize it and will fail to start.
Note: Applications that bundle their own Java runtime, such as Jenkins, Jira, Confluence, Keycloak, and Artifactory, require the bundled runtime to be updated by the application vendor or by replacing the runtime with a patched version.
Finding exposed Java services with runZero #
From the Services Inventory, use the following query to locate potentially impacted assets:
(_asset.protocol:=http AND protocol:=http AND http.head.cookieNames:"JSESSIONID") OR
(_asset.protocol:tls AND protocol:tls AND
(tls.stack:="java:8u272^14.0.2u12" OR tls.stack:="java:15.0.1^25.01"))
Note: This query identifies web and TLS services that appear to be running on Java, but it cannot determine the Java version or distribution in use. Results may include services that are not affected, such as those running unaffected or already patched Java releases, and should be verified against the affected versions above.