Introduction
Java4Shell (CVE-2026-114938) is a critical vulnerability in the Base64 decoder of the Java Virtual Machine (JVM). The Common Vulnerability Scoring System (CVSS) version 4.0 rates it 9.2. Malformed Base64 input corrupts memory and leads to remote code execution.
The vulnerability affects Java 17, 21 and 25 on x86-64 central processing units (CPUs) that support Advanced Vector Extensions 512 Vector Byte Manipulation Instructions (AVX-512 VBMI). Java 11 and ARM64 hosts are not affected.
This article covers apps that run on infrastructure the organization manages. Mendix Cloud and Mendix Cloud Dedicated apps are already protected, and redeploying them is still recommended. Public KBA: Impact of Java4Shell (CVE-2026-114938) vulnerability on Mendix Cloud
Environment
- Applications hosted in Mendix on Kubernetes
- Applications hosted in Mendix on Azure
- Private Mendix Platform
- Applications hosted in SAP Business Technology Platform
- Applications hosted in On-Premises
- Applications deployed with Docker
Instructions/Procedure
Select the section that matches the platform.
Mendix on Kubernetes, Mendix on Azure and Private Mendix Platform
Red Hat provides the fix in the ubi8 and ubi9 Universal Base Image (UBI) base images. Mendix on Azure uses ubi9. To apply the fix, redeploy each affected app:
- Check the base image of the environment in the runtime base image documentation.
- Create a new deployment package (.mda) of the app.
- Deploy the package. The deployment rebuilds the app image on the patched base image.
On Private Mendix Platform, rebuild the images of apps in user environments with the same steps. Release 2.8.2 addresses the portal itself and is planned.
The fix is not available yet for the Red Hat Hardened Image base image. Apply the JVM option until Red Hat publishes the update.
SAP Business Technology Platform
Until an update is available, add -XX:-UseBASE64Intrinsics to the JAVA_OPTS environment variable and apply the changes.
On-premises servers, Docker and Mendix Portable Runtime
These deployments use a Java installation that the organization manages. Install a fixed release from the Java vendor, or add -XX:-UseBASE64Intrinsics to the JVM arguments that start the app and restart the app. [CONFIRM: steps per deployment type.]
Apply the JVM option
The -XX:-UseBASE64Intrinsics option disables the vulnerable code, regardless of the hardware. A restart applies it, and a rebuild is not required. For Mendix on Kubernetes, Mendix on Azure and Private Mendix Platform, follow these steps:
- Add
-XX:-UseBASE64Intrinsicsto Custom JVM Options of the environment. - Restart the app.
No central setting applies the option to all environments, so repeat the steps for each environment. Do not use -XX:UseAVX=2 instead, because the JVM fails to start on ARM64 hosts.
Outcome
After the app runs on a patched base image or Java release, or after the JVM option is applied and the app restarts, the app no longer runs the vulnerable Base64 code.
Additional information
- Mendix documentation:
- Other documentation: Red Hat security bulletin RHSB-2026-018
- Related KBA: Impact of Java4Shell (CVE-2026-114938) vulnerability on Mendix Cloud
0 Comments