CyberSecurityNews

Critical Java4Shell Flaw Lets Hackers Execute Code Without Authentication on OpenJDK Servers


A critical flaw in OpenJDK’s Base64 decoder can let a remote attacker run code on an affected server without signing in. The vulnerability, dubbed Java4Shell and tracked as CVE-2026-114938, can also crash the Java Virtual Machine (JVM) or expose sensitive data held in its memory.

Oracle released security updates on November 17, 2026, and the U.S. Cybersecurity and Infrastructure Security Agency (CISA) urged organizations to patch immediately.

The flaw sits in HotSpot, the JVM that runs Java applications in many OpenJDK distributions. That differs from Log4Shell, which affected the Log4j logging library. Updating an application’s Java libraries will not replace a vulnerable runtime. Administrators need to identify the Java build each service actually runs, including any copy shipped by the application vendor.

Security firm Calif rated Java4Shell 9.2 under CVSS 4.0, which puts it in the critical range. OpenJDK’s advisory lists a score of 8.1 under CVSS 3.1. The scores use different versions of the severity standard. Both describe a serious flaw, but neither means every Java server can be exploited. Exposure depends on the runtime, the processor, and how the application handles outside data.

Calif researcher Quang Luong found the flaw while examining OpenJDK HotSpot with help from an AI coding tool. The disclosure follows Calif’s work on PHP2Shell and the emergency PHP patches. Both investigations found memory flaws in shared runtimes, but the PHP flaws and Java4Shell have different causes and require separate fixes.

Base64 represents binary data as text so applications can pass it through systems that expect text. It is common in sign-in flows, file uploads, and network messages.

On supported processors, HotSpot uses a faster decoder that handles several bytes at once. A mistake in that code can make the decoder write past the end of its allocated buffer before Java rejects the bad input. Rejecting it does not undo the memory damage.

Java4Shell Exposes Java Applications

Calif reported remote code execution without a login in default test setups of Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate. Its tests against Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker required authentication. The researchers also demonstrated code execution in sample applications built with Apache Struts and Spring Boot. These results describe the setups Calif tested, not every installation of those products.

The risk is not limited to servers that accept incoming requests. Calif also reported a client-side demonstration in which a Java program could be compromised after opening an encrypted TLS connection to a malicious server.

The researchers compared the memory exposure to Heartbleed because a successful attack could reveal data already held by the process, such as session tokens or private keys. The two flaws do not share the same cause.

The vulnerable decoder requires an x86-64 processor with AVX-512 VBMI support, a feature available on some Intel Xeon and newer AMD processors. ARM64 systems are not affected by this code path. The earlier Cybersecurity News report on the Java 17 flaw focused on that release line. The OpenJDK advisory now identifies fixes for Java 17, 21, 25 and 27. Oracle also lists a specific Java 8 Enterprise Performance Pack build and certain GraalVM builds as affected.

There is no single exploit that works across all Java applications, according to Calif. WatchTowr also expects attacks to be tailored to individual products because the CPU, JDK, and the way the application uses Base64 all matter. The research demonstrations establish that code execution is possible, but they are not evidence of attacks against production systems.

How to patch Java4Shell and Fix Versions

Oracle’s fixed Java SE releases include 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Organizations using Amazon Corretto, Eclipse Temurin, Azul Zulu or another distribution should check their vendor’s advisory for the build that fixes this CVE.

ProductAffected build listed for this CVEPatched build or upgrade guidance
Oracle Java SE 1717.0.21.0.317.0.21.1
Oracle Java SE 2121.0.13.0.321.0.13.1
Oracle Java SE 2525.0.5.0.325.0.5.1
Oracle Java SE 2727.0.1.0.327.0.1.1
Oracle Java 8 Enterprise Performance Pack8u511b33-perfInstall Oracle’s November 17 security update for the Enterprise Performance Pack. Verify the exact build in Oracle’s advisory.
Oracle GraalVM for JDK 1717.0.21.0.3Install Oracle’s November 17 security update for GraalVM for JDK 17.
Oracle GraalVM for JDK 2121.0.13.0.3Install Oracle’s November 17 security update for GraalVM for JDK 21.
Oracle GraalVM Enterprise Edition21.3.20.0.3Install Oracle’s November 17 security update for GraalVM Enterprise Edition.

CISA recommends patching internet-facing systems first and checking for runtimes bundled with third-party software, container images, and appliances. Those copies may not appear as separate entries in a software inventory.

Where patching must wait, Calif recommends starting affected JVMs with -XX:-UseBASE64Intrinsics to turn off the optimized Base64 routines. Another option on x86-64 is -XX:UseAVX=2, which disables AVX-512. Do not add the second flag to ARM startup settings because it can prevent Java from starting.

CISA also recommends restricting unauthenticated access, validating Base64 input before it reaches the decoder, and enforcing input-size limits while teams prepare updates. These are temporary controls, not replacements for a patched runtime.

After updating, restart each affected service or redeploy it with a rebuilt container image. Verify the version used by the running process rather than checking only the host’s default Java installation.

CISA also recommends watching for unexpected JVM crashes, unapproved runtimes, and suspicious Java processes. A crash alone does not prove exploitation, but an unexplained crash on an exposed, unpatched system deserves investigation.

What Are Leading Organizations Doing About AI and Cyber Risks? Find Out. View Details!



Source link