<-- Back

How to mitigate the Java4Shell vulnerability (CVE-2026-114938) in Mendix on Kubernetes, On-premises, and Docker

Introduction

This article describes how to identify the hosts that Java4Shell (CVE-2026-114938) affects and how to mitigate the vulnerability for Mendix apps that run on infrastructure the organization manages. CVE stands for Common Vulnerabilities and Exposures. This affects applications running on a Java distribution that the vendor lists as affected by CVE-2026-114938 

Java4Shell is a vulnerability in the Base64 decoder of the Java Virtual Machine (JVM) in the Open Java Development Kit (OpenJDK). The Common Vulnerability Scoring System (CVSS) version 4.0 rates it 9.2 (Critical). Malformed Base64 input can corrupt memory and lead to remote code execution. An attack requires attacker-controlled input to reach the vulnerable code path.

The vulnerable code is hardware-specific. The JVM runs it on x86-64 CPU that support Advanced Vector Extensions 512 Vector Byte Manipulation Instructions (AVX-512 VBMI). Hosts without this CPU feature, including ARM64 hosts, do not run the vulnerable code.

The vulnerable code comes from the OpenJDK source. Any Java distribution built from it can be affected, including Oracle JDK, Eclipse Temurin and other vendor builds. Early reports named OpenJDK 17.0.6 and later. Oracle lists additional Java releases in its November 2026 security update. See the advisory of the Java distribution vendor for the affected versions.

Mendix manages Mendix Cloud environments. For their status, see the Mendix status page.

Environment

  • Applications hosted in Mendix on Kubernetes
  • Applications hosted in On-Premises
  • Applications deployed with Docker

Instructions/Procedure

Identify the affected hosts, then apply one mitigation to each affected host.

  1. Check whether the host is affected.
    • On Linux, run this command on each host or node that runs the app: grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'. If the output lists avx512vbmi, the CPU is affected.
  2. Apply one of these mitigations:
    • Update to the latest security release of the Java distribution in use, as listed in the vendor advisory. 
    • Add -XX:-UseBASE64Intrinsics to the JVM options. This option disables the hardware-accelerated Base64 code.
    • Add -XX:UseAVX=2 to the JVM options. This option disables AVX-512. Apply it to x86-64 hosts. On ARM hosts, the JVM does not recognize the option and fails to start.
    • Move the app to hardware without AVX-512 VBMI, such as ARM64.
  3. Restart the app to apply the JVM option changes.
  4. Run the check from step 1 again. After a mitigation option, the UseAVX value is 2 or lower, or UseBASE64Intrinsics is false. 

Outcome

After the mitigation, the app no longer runs the vulnerable Base64 code on the mitigated host. 

Internal information related

C0CJM375917

Additional information

Have more questions? Submit a request

0 Comments

Article is closed for comments.

To provide feedback, please open a ticket here. Don't forget to include the article's URL along with the feedback you would like to provide.