|
Component |
Keycloak |
|---|---|
|
Version |
Current versions with Keycloak on edoc platform |
|
Created on |
|
|
Last modified on |
No Workflow Applied |
|
Review status |
No Workflow Applied |
|
KB article number |
2793013324 |
Summary
In this Knowledge Base article, we provide the latest information on the CVE-2026-114938 vulnerability, also known as Java4Shell. The vulnerability affects the Java Runtime Environment and, under certain conditions, could allow remote code execution. This vulnerability is relevant to edoc because edoc platform uses Keycloak.
CVE-2026-114938 was rated "critical" with a score of 9.2/10 under CVSSv4.0 and "high" with a score of 8.1/10 under CVSSv3.1. Based on current information, exploitability depends on specific x86-64 processors with AVX-512-VBMI support.
The recommended mitigation is now available in the current edoc agent (edoc platform). You can apply the mitigation by performing a synchronization. As soon as additional Java or Keycloak updates become available and are approved by edoc, we will provide information about the affected versions, the release date, and the necessary steps to take.
Additional information online:
-
https://www.keycloak.org/2026/11/java4shell-vulnerability-cve-2026-114938
-
BSI Cybersecurity Alert (in German only)
Updates to this article
|
Date and time |
Description |
|---|---|
|
2026-11-19 |
|
|
2026-11-19 |
|
Current situation
The published information describes a critical memory corruption vulnerability in the Java Runtime Environment. The vulnerability affects an optimized processing feature in the Java compiler on certain x86-64 processors with AVX-512 VBMI support.
Under certain conditions, unauthenticated users can send specially crafted input over the network to a vulnerable Java application. A successful exploit can lead to the execution of malicious code and, consequently, the complete compromise of the affected Java process.
edoc platform uses Keycloak. According to the vendor's information, Keycloak is affected by this vulnerability. The recommended mitigation is included in the latest version of edoc agent and can be applied by performing a synchronization.
Impact on edoc products
As things stand, Keycloak is relevant in the current versions of the edoc platform. Whether a specific system is vulnerable to CVE-2026-114938 also depends on CPU support for AVX-512 VBMI and the respective Java and Keycloak configurations.
edoc365 customers
The edoc365 systems are automatically evaluated and updated by the relevant edoc team.
On-premises customers
On-premises installations are not updated centrally by edoc. To address the security vulnerability, you must use the latest edoc agent and perform a synchronization so that the released mitigation is applied. The mitigation is performed only for Keycloak versions 24 and 26. These Keycloak versions were installed starting with an edoc 365 business process platform version higher than 25.1.6.1. The technical assessment and necessary updates will be carried out together as part of the scheduled update.
Recommended precautions
First, check whether your system uses an affected processor that supports AVX-512 VBMI. On Ubuntu, for example, you can check for the availability of AVX-512 VBMI using the following command in Bash:
grep -m1 '^flags' /proc/cpuinfo | grep -qw avx512vbmi && echo 'AVX-512 VBMI available'
If no output is generated, the tested system does not support the affected CPU function and, based on current information, is not considered vulnerable to this vulnerability.
If an affected configuration is detected, a JVM mitigation is available. The JVM mitigation disables the affected hardware-accelerated Base64 processing path. The recommended mitigation is included in the latest version of the edoc agent.
After the automatic update of edoc agent, running the SyncSystemState task from edoc system control implements the mitigation. As of now, no update to edoc platform releases is required for this.
Until the approved mitigation is implemented, we recommend limiting access to the edoc platform web server as much as possible. In particular, access to HTTPS/Port 443 should be restricted to only those networks, user groups, or upstream security systems that require it.
This measure reduces the attack surface for unauthenticated attacks from the Internet, but does not replace the application of the approved mitigation or the installation of subsequent security updates.
Please evaluate the implementation based on your infrastructure and business requirements.
Measures completed and planned by edoc
As of November 19, 2026, the recommended mitigation is included in the current version of edoc agent. Customers can apply the mitigation by performing a synchronization.
edoc continues to check for available Java and Keycloak updates for the supported release channels of edoc platform and will provide information on the next steps as soon as additional approved patch versions become available.
Current status
-
CVE-2026-114938 is rated as a critical or high-severity vulnerability.
-
The vulnerability affects Java applications under certain technical conditions, particularly certain x86-64 processors with AVX-512-VBMI support.
-
Based on current information, Keycloak in edoc platform is relevant.
-
The recommended mitigation is included in the current edoc agent and can be applied by performing a synchronization.
-
edoc365 systems are automatically evaluated and updated by edoc.
-
On-premises customers should check for CPU impact, use the latest edoc agent, and perform a synchronization to apply the mitigation. Until then, access to HTTPS/Port 443 on the edoc platform should be limited as much as possible.
Support and Managed Services
If you have any questions or encounter technical issues, please open a ticket through our customer portal and include the reference CVE-2026-114938.
If you are covered by a managed services contract, edoc will proactively contact you to conduct a customized assessment and coordinate next steps.