Skip to content
Java4Shell Vulnerability Affects Keycloak Deployments

Java4Shell Vulnerability Affects Keycloak Deployments

First seen 18 Nov 2026, 15:46 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 18, 2026 at 15:47 UTC
  • •CVE-2026-114938 allows remote code execution in Keycloak before authentication.
  • •Affected systems include Keycloak instances running unpatched OpenJDK 17.0.6 and later.
  • •Immediate mitigation involves disabling Base64 intrinsics in Keycloak startup scripts.

A vulnerability (CVE-2026-114938), dubbed Java4Shell, has been disclosed affecting Keycloak instances using OpenJDK's Base64 decoder on x86-64 processors with AVX-512 VBMI support. The flaw allows for pre-authentication remote code execution, enabling attackers to exploit the vulnerability before user authentication occurs. Keycloak administrators are advised to check their Java runtime and CPU configurations, particularly those using unpatched OpenJDK builds from version 17.0.6 onward. To mitigate the risk, it is recommended to disable the vulnerable Base64 intrinsics by adding the JVM flag -XX:-UseBASE64Intrinsics to startup scripts. The vulnerability was published on November 17, 2026, with proof-of-concept code becoming available on November 18, 2026. Organizations running affected Keycloak instances must act quickly to assess their exposure and implement mitigations.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-17
CVE-2026-114938 published
A critical vulnerability affecting Keycloak and OpenJDK's Base64 decoder was disclosed.
Keycloak
2026-11-18
Proof-of-concept code released
Security researchers demonstrated the exploit against Keycloak, confirming the vulnerability's severity.
github.com

More articles in this cluster (3)

Following this threat?

Track CVE-2026-114938 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

What versions of Keycloak are affected?
Keycloak instances running unpatched OpenJDK builds from version 17.0.6 onward are at risk.
How can I mitigate this vulnerability?
Add the JVM flag -XX:-UseBASE64Intrinsics to Keycloak startup scripts to disable the vulnerable Base64 intrinsics.
Is there active exploitation of this vulnerability?
While proof-of-concept code exists, there are no confirmed reports of exploitation in the wild yet.