Java4Shell: Java flaw puts Keycloak and other applications at
Java4Shell is a critical Java vulnerability that can crash applications or allow attackers to run code remotely, and CISA is urging organizations to patch immediately. The flaw, tracked as CVE-2026-114938, has a CVSS severity score of 8.1. CVSS is a standard system for rating how serious a security flaw is.
The vulnerability is an out-of-bounds write, meaning software can write data beyond the memory area assigned to it. It affects the Base64 decoder in the x86-64 HotSpot Java Virtual Machine, or JVM, the software that runs Java programs on compatible 64-bit processors. The affected component is part of the Java Development Kit, or JDK, which contains the tools and runtime software used to build and run Java applications.
According to CISA, specially crafted Base64 input can crash the JVM and may allow unauthenticated remote code execution. Unauthenticated means the attacker does not need an account or login. The flaw can therefore result in denial of service, where a service becomes unavailable, or remote code execution, where an attacker makes the affected system run arbitrary commands. The relevant vendor and OpenJDK have released patches, and there is no evidence so far that CVE-2026-114938 has been exploited in the wild.
Under default settings, Java4Shell can allow attackers without an account to execute arbitrary code on Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. With a login, the flaw can affect Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. Security and software advisories have also been published by Aikido, Amazon Linux, Blackpoint Cyber, Chainguard, Cisco Talos, Cycode, Datadog, Dynatrace, Endor Labs, Field Effect, Hadrian, Horizon3.ai, Miggo, Orca Security, Qualys, Rapid7, Red Hat, SentinelOne, Sophos, Tanium, Tenable, Upwind, VulnCheck, watchTowr and Wiz.
Keycloak provided more specific guidance in an update dated November 18, 2026. A Keycloak installation may be at risk when it uses an unpatched OpenJDK build from 17.0.6 onward, including unpatched OpenJDK 21 and 25 builds; when its x86-64 host or virtual machine exposes the AVX-512 VBMI CPU feature to Java; and when the JVM has Base64 performance optimisations enabled and has not been limited to AVX2 with the setting -XX:UseAVX=2.
The x86-64 Keycloak container images tagged 26.8.2-1 and 26.8.2-2 include an affected OpenJDK 21.0.13 build. However, those image tags alone do not prove that an installation is exploitable. Administrators also need to check the CPU feature and the JVM settings in use. A Keycloak ZIP or TAR.GZ installation started directly on a host can also be affected, because the relevant conditions depend on the Java runtime and CPU rather than on whether the application runs inside a container.
Keycloak recommends checking the CPU feature on a host or virtual machine with this command:
grep -m1 '^flags' /proc/cpuinfo | grep -qw avx512vbmi && echo 'AVX-512 VBMI available'
If the command produces no output, the CPU does not expose AVX-512 VBMI and is not known to be affected by the flaw. Keycloak has released temporary mitigations for users to apply while it prepares updated Keycloak and Keycloak Operator container images containing patched OpenJDK builds.
Blackpoint Cyber researchers reported that the vulnerability could also be reached through a local Spring Boot application using Spring Security. In their testing, about 28,000 unauthenticated HTTP requests containing a malformed Base64 authentication value caused the JVM to terminate after roughly 20 seconds of sustained requests. Further testing showed corruption of nearby Java objects and changes to live application data without an immediate crash necessarily occurring.
CISA advises organizations to identify affected Java installations and review software inventories for JDKs and Java runtimes. That review should include Java bundled with third-party applications, container images and appliances. Relevant Java and vendor patches should be applied as soon as they are available. Where immediate patching is not feasible, CISA recommends temporary controls such as restricting and validating Base64 input at the application boundary, enforcing input-size limits and limiting unauthenticated access.
AEU-I offers security-first IT, infrastructure and consulting, which is relevant to teams managing this kind of Java security risk.