CISA Calls for Immediate Patching of Java4Shell Java Flaw

The U.S. Cybersecurity and Infrastructure Security Agency has called on organizations to immediately patch Java4Shell, a critical Oracle Java vulnerability tracked as CVE-2026-114938 and assigned a CVSS score of 8.1. The flaw is an out-of-bounds write that can cause denial of service or, in certain conditions, permit remote code execution.
Oracle and OpenJDK have released patches. CISA said it had no evidence of exploitation in the wild at the time of its alert, but urged organisations to identify affected installations and deploy the relevant Java and vendor fixes as soon as possible.
A flaw in the HotSpot JVM Base64 decoder
Java4Shell affects the Base64 decoder in the x86-64 HotSpot Java Virtual Machine, which forms part of the Java Development Kit. CISA described it as a critical memory-corruption vulnerability: specially crafted Base64 input could crash the JVM and potentially allow unauthenticated remote code execution.
The issue matters because Java runtimes are often installed beyond a centrally managed JDK deployment. They may be bundled with third-party applications, incorporated into container images, or embedded in appliances. A software inventory that only tracks standalone Java installations can therefore miss systems that require remediation.
Reported testing indicates that the vulnerability can expose several widely deployed enterprise products. Under default settings, an attacker without an account may be able to execute arbitrary code on Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. Products cited as requiring a login include Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker.
Testing highlights application-level exposure
Blackpoint Cyber researchers Sam Decker and Nevan Beal said the flaw could be reached through a local Spring Boot application using Spring Security. In their test environment, approximately 28,000 unauthenticated HTTP requests with a malformed Base64 authentication value caused the JVM to terminate after roughly 20 seconds of sustained traffic.
The researchers also reported corruption of nearby Java objects and changes to live application data without an immediate crash. That observation reinforces why a service remaining available is not, by itself, proof that malformed input has had no effect.
Actions for Java estate owners
CISA recommends first identifying affected JDKs and Java runtimes across the estate, including components delivered inside applications, images and appliances. Teams should then apply Oracle, OpenJDK and relevant vendor patches as they become available.
Where immediate patching is not feasible, CISA advises temporary compensating controls: restrict and validate Base64 input at the application boundary, enforce input-size limits, and limit unauthenticated access. The practical business implication is to treat Java runtime discovery and patch verification as an application-and-platform task, rather than relying solely on endpoint software inventories.

