Java4Shell fixes released for OpenJDK and Keycloak containers
TL;DR - Update: Keycloak 26.8 container images now use Red Hat OpenJDK 21.0.13.1, and fixed OpenJDK builds include 17.0.21.1, 21.0.13.1, and 25.0.5.1. - CISA says CVE-2026-114938, known as Java4Shell, can allow unauthenticated remote code execution through specially crafted Base64 input. - The flaw affects the accelerated Base64 decoder in the x86-64 HotSpot JVM under specific runtime, CPU, and JVM conditions. - Researchers report pre-authentication RCE demonstrations against applications including Jira, Jenkins, and Keycloak. - Exploitation in the wild has not been established in the supplied material.
What happened#
CVE-2026-114938, known as Java4Shell, is a memory-corruption vulnerability in the accelerated Base64 decoder of the x86-64 HotSpot Java Virtual Machine. CISA says specially crafted Base64 input could crash the JVM and allow unauthenticated remote code execution. The affected JVM is part of the Java Development Kit. (CISA)
OpenJDK lists the issue under the hotspot/ compiler component with a CVSSv3.1 vector of 8.1 NHNNUHHH. Its affected-version statement lists 27.0.1.0.3, 25.0.5.0.3, 21.0.13.0.3, 17.0.21.0.3, 11.0.33, 8u512, and earlier. The risk matrix marks CVE-2026-114938 for Java lines 8, 11, 17, and 21. (OpenJDK)
Keycloak says the flaw is in OpenJDK’s accelerated Base64 decoder. It processes some requests before authentication, so an affected Keycloak deployment should not assume that a login requirement prevents exposure. Keycloak identifies three conditions for risk: an unpatched OpenJDK build from 17.0.6 onward, an x86-64 host exposing avx512vbmi to Java, and an enabled Base64 intrinsic path that has not been limited to AVX2 with -XX:UseAVX=2. (Keycloak)
Fixed versions are now identified by Keycloak as 17.0.21.1, 21.0.13.1, and 25.0.5.1. Keycloak also says its 26.8 container images were updated to Red Hat OpenJDK 21.0.13.1. The updated tags include latest, 26.8, 26.8.2, and 26.8.2-3. (Keycloak)
Are you affected#
Organizations should review every Java installation, including JDKs and runtimes bundled with third-party applications, container images, and appliances. CISA notes that these runtimes may not appear as separate software-inventory entries.
For Keycloak, check every node or virtual machine that can run the service, including failover nodes and nodes used during rolling updates. Keycloak says x86-64 container images tagged 26.8.2-1 and 26.8.2-2, as checked on 18 November 2026, bundled an affected OpenJDK 21.0.13 build. The image tags alone do not establish exploitability. The CPU feature and effective JVM flags also need to be checked. The updated tags include latest, 26.8, 26.8.2, and 26.8.2-3, which use Red Hat OpenJDK 21.0.13.1. (Keycloak)
Keycloak says a deployment is at risk when all of its listed conditions apply. A ZIP or TAR.GZ installation can also be affected because exposure depends on the Java runtime and CPU, not on whether the service runs in a container.
The issue is not established for every Java application. Exposure depends on whether the application passes attacker-controlled Base64 data to the affected decoder and whether that processing occurs before authentication. SentinelOne reports that Calif demonstrated pre-authentication RCE in default configurations of Apache Kafka Broker, Atlassian Confluence and Jira, JFrog Artifactory, Jenkins, Keycloak, Gerrit, PingFederate, and Spring Boot applications, with post-authentication execution against Elasticsearch. (SentinelOne)
What is confirmed and what is reported#
| Claim | Source | Status |
|---|---|---|
| CVE-2026-114938 is a memory-corruption vulnerability in the x86-64 HotSpot JVM’s accelerated Base64 decoder. | CISA, Keycloak | Confirmed |
| Specially crafted Base64 input can crash the JVM and allow unauthenticated remote code execution. | CISA | Confirmed |
OpenJDK lists CVSSv3.1 vector 8.1 NHNNUHHH for CVE-2026-114938. |
OpenJDK | Confirmed |
| Keycloak can process Base64 data before authentication, and affected instances should not rely on login requirements as protection. | Keycloak | Confirmed |
Keycloak 26.8 container images use Red Hat OpenJDK 21.0.13.1, and fixed versions include 17.0.21.1, 21.0.13.1, and 25.0.5.1. |
Keycloak | Confirmed |
| Calif demonstrated pre-authentication RCE against Jira, Jenkins, Keycloak, and other applications. | SentinelOne | Reported |
| Oracle released patches addressing the flaw in its November 2026 Critical Security Patch Update. | SentinelOne | Reported |
| Exploitation in the wild has been reported. | No published confirmation in the cited material | Reported status not established |
What defenders should do now#
-
Identify all Java installations, including bundled runtimes, container images, appliances, failover nodes, and systems used during rolling updates.
-
Prioritize internet-facing systems and authentication services. Review the Java runtime and CPU type used by each deployment rather than relying only on the application version.
-
Apply a vendor-confirmed fixed runtime as soon as it is available. Keycloak identifies
17.0.21.1,21.0.13.1, and25.0.5.1as fixed OpenJDK versions. Keycloak 26.8 container users can use updated tags includinglatest,26.8,26.8.2, and26.8.2-3, which use Red Hat OpenJDK21.0.13.1. (Keycloak) -
For Keycloak, check whether the host or virtual machine exposes
avx512vbmito Java. Repeat the check on the node executing a container, not only on an administrator workstation. -
For affected Keycloak JVMs, Keycloak says to use the interim mitigation
-XX:-UseBASE64Intrinsicsand restart every instance. Keycloak identifies this as Red Hat’s preferred interim mitigation. -
Verify the effective setting in the running JVM. Keycloak says the live process must report
UseBASE64Intrinsics = false; seeing the variable in a service or container environment is not sufficient. -
If immediate patching is not feasible, CISA recommends temporary compensating controls, including restricting and validating Base64 input at the application boundary, enforcing input-size limits, and limiting unauthenticated access. (CISA)
-
Monitor for suspicious activity, including rogue runtimes, unexpected JVM crashes, and suspicious Java processes. Keep interim mitigations in place until a vendor-confirmed fixed runtime has been deployed and verified on every relevant instance.
This advisory is informational and is updated as vendors publish details. Confirm versions and actions against the vendor’s own guidance for your environment.
This advisory is informational and is updated as vendors publish details. Confirm versions and actions against the vendor’s own guidance for your environment.
Sources
- Primary notice: cisa.gov
- Primary notice: keycloak.org
- Primary notice: openjdk.org
- Research: sentinelone.com
- Research: endorlabs.com
- Report: thehackernews.com