Java4Shell HotSpot Flaw Causes Heap Corruption; Researchers Demonstrate RCE

· Original article ↗

Summary

CVE-2026-114938 (“Java4Shell”) is an integer-underflow flaw in x86-64 HotSpot’s Base64 decoder. Researchers demonstrated RCE under specific Java, CPU and input conditions; public exploitation is unconfirmed. Fixed Java releases are available.

Key points

  • The flaw affects the x86-64 HotSpot Base64 decoder and can cause an out-of-bounds heap write when processing malformed Base64 input.
  • Researchers demonstrated remote code execution, but no publicly confirmed exploitation has been reported.
  • Exposure requires an affected Java release, supported AVX-512 hardware, and attacker-controlled Base64 input reaching the decoder before validation.
  • Affected releases include Java 17.0.6 and later Java 17 releases, and feature releases beginning with Java 18; Java 8, Java 11, and Java 17.0.5 and earlier are not affected.
  • Oracle and Amazon released fixed Java versions; organizations are advised to inventory bundled runtimes and prioritize internet-facing systems.
  • The article says CVE-2026-114938 was not listed in CISA’s Known Exploited Vulnerabilities catalog at the time of writing.

Article Details

Vulnerability Types
  • Integer underflow
  • Out-of-bounds write
  • Memory corruption
Severity
Critical; CVSS v4 score 9.2
Affected Versions
  • OpenJDK 17.0.6 and later Java 17 releases
  • Java feature releases beginning with Java 18, including Java 21, Java 25, and Java 27
Exploitation Status
not_reported
Exploit Availability
public_poc
Patch Status
available
Workarounds
  • Restrict exposure to untrusted Base64 input where updates cannot be applied.
  • Use input validation, request filtering, and length restrictions; limit unauthenticated access.

MITRE ATT&CK

CVE

Vendors

Products

Amazon Correttoreference implementation of Java SE, serves as the code base for Oracle JDK, Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Red Hat Build of OpenJDK, SAP Machine, BellSoft Liberica, andAtlassian Confluencesuccessfully reproduced exploitation against default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate, illustrating the potential reach of theAtlassian Jirademonstrations have successfully reproduced exploitation against default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate, illustrating the potential reachJava SEOpenJDK, the open-source reference implementation of Java SE, serves as the code base for Oracle JDK, Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Red Hat Build of OpenJDK, SAP Machine,Jenkinsagainst default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate, illustrating the potential reach of the vulnerability across widely deployedJFrog Artifactoryexploitation against default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate, illustrating the potential reach of the vulnerability across widelyKeycloakresearcher demonstrations have successfully reproduced exploitation against default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate, illustrating theOpenJDKOpenJDK, the open-source reference implementation of Java SE, serves as the code base for Oracle JDK, Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Red Hat Build of OpenJDK, SAP Machine,Oracle JDKOpenJDK, the open-source reference implementation of Java SE, serves as the code base for Oracle JDK, Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Red Hat Build of OpenJDK, SAP Machine,PingFederateconfigurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate, illustrating the potential reach of the vulnerability across widely deployed enterprise applications.

Countries

Related Articles