A newly discovered vulnerability in OpenJDK’s Base64 decoder, dubbed “Java4Shell” and tracked as CVE-2026-114938, allows remote attackers to execute code on affected servers without authentication. Depending on the situation, it can also crash the Java Virtual Machine or expose sensitive data stored in its memory. The issue was addressed by Oracle with security updates released on November 17, 2026, and the U.S. Cybersecurity and Infrastructure Security Agency (CISA) has called for immediate patching.
What the Flaw Is and Where It Lives
The flaw lies in HotSpot, the Java Virtual Machine (JVM) runtime used in many OpenJDK distributions. While this is not another Log4Shell (which affected the Log4j library), the vulnerability is within the Base64 decoding logic in HotSpot, not a higher-level library. This means that even if you update application-level dependencies, vulnerable Java runtimes still pose risks. Each service’s actual Java build— including those bundled with applications, containers, or appliances—must be inspected.
Two different severity scores highlight the seriousness: Calif, the security firm that found Java4Shell, rated it 9.2 under CVSS v4.0, placing it firmly in the critical range. OpenJDK’s own advisory gives it an 8.1 under CVSS v3.1. But not every Java server is equally at risk—vulnerability depends heavily on factors like CPU architecture, runtime details, and how Base64 decoding is used in practice. Some servers may be exposed via client-side interactions or incoming requests; others may need authentication.
How It Can Be Exploited & Who’s Affected
Testing from Calif uncovered remote code execution without authentication in default setups of Keycloak, Atlassian Jira, Confluence, JFrog Artifactory, Jenkins, and PingFederate. In contrast, tests against Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker needed authentication for exploitation. Sample applications built with frameworks like Apache Struts and Spring Boot were also vulnerable in lab setups. The threat isn’t purely theoretical: in some cases, malicious Java programs connected over TLS could be compromised even from the client side.
The flaw is specific to x86-64 processors with AVX-512 VBMI support—seen in certain Intel Xeon and newer AMD chips. Systems using ARM64 architectures are not impacted by this code path. Multiple Java releases are affected, including Java 8 Enterprise Performance Pack, 17, 21, 25, 27, and several builds of GraalVM.
Mitigations and Fixes
Oracle’s release of patched versions—17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1—is the primary fix. Users of Java 8 Enterprise Performance Pack or affected GraalVM builds should apply the Nov. 17 security update.
While awaiting upgrades, temporary defenses include disabling the faulty Base64 intrinsic routines via configuration flags (e.g., setting the JVM flag -XX:-UseBASE64Intrinsics), or on x86-64 systems, disabling AVX-512 using -XX:UseAVX=2. These are stopgaps—not substitutes for patched runtimes. It’s also recommended to limit unauthenticated access, validate Base64 input carefully, enforce input‐size limits, and watch for abnormal JVM crashes or unusual process behavior.
After installing updates, services or containers should be restarted or redeployed to ensure the new Java runtime is in use. Do not rely solely on system package versions—check the runtime version of each Java process directly. CISA underscores this as crucial for internet-facing systems and any Java runtime embedded within third-party software.
With the Oracle fixes in place, organizations should verify patched builds, especially for Java lines 8 (Enterprise Performance Pack), 17, 21, 25, 27, and corresponding GraalVM versions. Systems using ARM64 processors are largely unaffected by the problematic code path tied to AVX-512 VBMI, so risk is lower, but vigilance is still advised.
This flaw is among several recent vulnerabilities exposing shared runtimes through memory corruption. While Java4Shell does not mirror the cause of Log4Shell or earlier flaws, its size underscores how even common, foundational primitives like Base64 decoding can hide critical weaknesses. As memory disclosure risks resemble those of Heartbleed, the stakes are high for session tokens, private keys, and other sensitive data resident in JVM memory.
Why This Matters
Java remains one of the most widely used platforms for enterprise and web applications. JVM runtimes power everything from server backends to embedded devices. A vulnerability allowing unauthenticated remote code execution pushes the threat surface well beyond conventional attack vectors. For organizations relying on bundled or vendor-supplied Java, Java4Shell exposes a blind spot: patching dependencies is not enough when the runtime itself permits abuse.
What to Watch Next
Expect vendors to issue advisory updates, and keep an eye out for proof-of-concepts or exploits in the wild. Monitor your environment for any unexpected JVM behavior. Longer term, the Java ecosystem may revisit how intrinsic decoding routines are shipped and whether hardware-specific accelerations need stricter verification. This could reshape how OpenJDK, GraalVM, and related distributions are built and secured.