Java4Shell (CVE-2026-114938): Status and mitigation for Quarkus users
|
This post is updated as the situation evolves. Last updated: 18 November 2026, 18:00 UTC |
TL;DR / Current status
-
Quarkus is not affected. The JDK is.
-
Native executables built with Mandrel are not affected.
-
Mandrel builder images: patched (workaround applied). Re-pull floating tags. Update pinned tags. See the available tags.
-
UBI Java runtime images: not yet fixed. Add
-XX:-UseBASE64Intrinsicsto the JVM options as workaround. -
JVM on bare metal: if your JDK is patched, you are fine. Otherwise, add
-XX:-UseBASE64Intrinsicsas workaround.
| Deployment model | Status | Action |
|---|---|---|
JVM on bare metal |
Depends on your JDK |
Upgrade the JDK, or add |
JVM in a container, UBI Java runtime image |
⚠️ Not fixed yet |
Add |
Native executable (Mandrel) |
✅ Not affected |
None |
Mandrel builder images |
✅ Patched |
Re-pull floating tags, update pinned tags |
The vulnerability
CVE-2026-114938, aka "Java4Shell", is a memory corruption bug in the OpenJDK Base64 decoder. The JVM uses a CPU-optimized implementation (an intrinsic) to decode Base64. A crafted Base64 input makes it write past its buffer. Researchers demonstrated memory disclosure and remote code execution.
Exploitation requires all of the following:
-
An unpatched OpenJDK 17.0.6+, 21, 25 or 27 build (all vendors: Temurin, Red Hat, Corretto, Zulu, etc.).
-
An x86-64 CPU exposing AVX-512 VBMI (on Linux:
avx512f,avx512bw,avx512vbmiandbmi2in/proc/cpuinfo). ARM64 is not affected. -
Base64 intrinsics enabled (the default).
-
The application decodes attacker-controlled Base64 data. Almost every HTTP application does decode Base64: Basic auth headers, JWTs, request payloads.
Oracle rates it CVSS 3.1 8.1. No exploitation in the wild is known at the time of writing.
References:
Is Quarkus affected?
No. The bug lives in the JDK, not in Quarkus. Upgrading Quarkus does not fix it. Fixing or mitigating the JDK does.
Mitigation per deployment model
JVM on bare metal
You run your Quarkus application with a JDK installed on the host.
-
If your JDK vendor shipped a fixed build and you installed it: you are fine.
-
Otherwise: add
-XX:-UseBASE64Intrinsicsto the JVM options.
java -XX:-UseBASE64Intrinsics -jar target/quarkus-app/quarkus-run.jar
Or, if you use JAVA_OPTS in your start scripts:
export JAVA_OPTS="$JAVA_OPTS -XX:-UseBASE64Intrinsics"
Remove the flag once a fixed JDK is deployed.
JVM in a container, UBI Java runtime image
This is the Quarkus recommended setup (Dockerfile.jvm, registry.access.redhat.com/ubi9/openjdk-<version>-runtime or registry.access.redhat.com/ubi10/openjdk-<version>-runtime).
The UBI Java runtime images are not fixed yet. We are waiting for updated images. We will update this post when they are available.
In the meantime, add -XX:-UseBASE64Intrinsics to JAVA_OPTS_APPEND.
Use JAVA_OPTS_APPEND, not JAVA_OPTS: overriding JAVA_OPTS drops the defaults computed by the image.
In your Dockerfile.jvm:
ENV JAVA_OPTS_APPEND="-Dquarkus.http.host=0.0.0.0 -Djava.util.logging.manager=org.jboss.logmanager.LogManager -XX:-UseBASE64Intrinsics"
Or at deployment time, without rebuilding the image (Kubernetes / OpenShift):
env:
- name: JAVA_OPTS_APPEND
value: "-Dquarkus.http.host=0.0.0.0 -Djava.util.logging.manager=org.jboss.logmanager.LogManager -XX:-UseBASE64Intrinsics"
If you use the Quarkus Kubernetes extension:
quarkus.kubernetes.env.vars.java-opts-append=-Dquarkus.http.host=0.0.0.0 -Djava.util.logging.manager=org.jboss.logmanager.LogManager -XX:-UseBASE64Intrinsics
Native executable compiled with Mandrel
Not affected. A native executable does not run on the HotSpot JVM and does not use the vulnerable intrinsic. No action needed.
Mandrel builder images
These images let you build a native executable without installing Mandrel (quarkus.native.container-build=true).
The resulting native executable is not affected, whatever image version built it.
The images themselves ship a JDK, used to run the native-image build.
They have been patched with the workaround (quarkus-images#344):
-
On amd64 images bundling an affected JDK (21 before 21.0.13.1, 25 before 25.0.5.1), the image sets
JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics. -
arm64 images are not affected and are unchanged.
-
Once the images bundle a fixed JDK, the workaround is dropped automatically.
Your build logs now show Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsics. This is expected.
If you override JAVA_TOOL_OPTIONS when running the builder image, you drop the workaround. Keep -XX:-UseBASE64Intrinsics in your value.
To get the patched image:
-
Floating tags (
jdk-21,jdk-25): re-pull the image. Docker and Podman do not re-pull automatically.docker pull quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:jdk-21 docker pull quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:jdk-25Use
podman pullwith the same arguments if you use Podman. Or setquarkus.native.container-runtime-options=--pull=always. -
Pinned tags: update to a patched tag:
-
JDK 21:
23.1.13.0-Final-java21-2026-11-18 -
JDK 25:
25.0.5.0-Final-java25-2026-11-18
-
To check that your local image is patched (amd64):
docker run --rm --entrypoint printenv quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:jdk-21 JAVA_TOOL_OPTIONS
docker run --rm --entrypoint printenv quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:jdk-25 JAVA_TOOL_OPTIONS
Expected output: -XX:-UseBASE64Intrinsics.
Verify the mitigation
Do not trust the environment variable alone. Check the running JVM:
jcmd <pid> VM.flags -all | grep UseBASE64Intrinsics
Expected output:
bool UseBASE64Intrinsics = false {product} {command line}
The origin at the end depends on how the flag is set: {command line} for JAVA_OPTS_APPEND or the java command, {environment} for JAVA_TOOL_OPTIONS.
What matters is UseBASE64Intrinsics = false.
In a container, run it with kubectl exec or docker exec.
The Quarkus process is usually PID 1.
Acknowledgements
Updates
-
18 November 2026, 18:00 UTC: Initial publication. Mandrel builder images (
jdk-21,jdk-25) patched at 13:15 UTC.