WildFly and Java4Shell
If your organization uses WildFly, even if you are not responsible for adminstering WildFly instances, please pass this post on to those who are.
We’ll update this post as we progress on the plans discussed below.
The Java4Shell flaw is in Java SE’s Base64 decoder, which WildFly uses in its handling of some requests.
Planned Releases to Address Java4Shell
The flaw is in Java SE, so the fixes the WildFly project can provide are updates to our container images that package Java SE. Our plans for that are as follows:
Container Images for Docker/Podman
For Docker and Podman users, WildFly publishes a wildfly container image at quay.io that users can use as a base for their own image incorporating their deployment.
We provide variants of the wildfly image that run on SE 21 and 25 by layering on top of the eclipse-temurin images.
Since our images layer on top of Temurin images, we can’t update them by updating an SE binary; we need the full Temurin image to be released. My understanding is Temurin binaries may be available before their images are.
We will publish updates of the wildfly images as soon as we have patched eclipse-temurin:21-ubi10-minimal and eclipse-temurin:25-ubi10-minimal images.
The status of Temurin releases can be tracked at their November 2026 Release Status page.
We plan to update the images for the following WildFly releases:
-
WildFly 42.0.1, which is in progress and expected to be released next Tuesday, November 24.
-
WildFly 41.0.1
|
Note
|
WildFly’s general support lifecycle states that we will produce a single micro bug-fix release for each major, and will not produce further updates once the next major is released. So, normally we would not do further updates for WildFly 41. Producing updates for the 41.0.1 images is outside our normal policies and is not something we expect to repeat. For more on our intentions regarding WildFly 41 maintenance, please see our WildFly 41 Maintenance Plans post. |
|
Note
|
For WildFly 41.0.1, we published both a |
OpenShift Images
WildFly provides wildfly-runtime images at quay.io that serve as a base layer into which a provisioned WildFly installation can be copied, using either Source-to-Image (S2I), our Helm Chart or your own Docker build.
We provide variants of the wildfly-runtime image that package OpenJDK 21 and 25.
On November 19, 2026, we published updates of the wildfly-runtime images that incorporate Java SE releases with the CVE-2026-114938 flaw fixed.
We also provide a wildfly-s2i image that is used in an S2I workflow. We provide variants of this image that package OpenJDK 21 and 25.
On November 19, 2026, we published updates of the wildfly-s2i images that incorporate Java SE releases with the CVE-2026-114938 flaw fixed.
Am I affected?
Consider a WildFly instance to be at risk when all of these apply:
-
It runs an unpatched Java SE build from 17.0.6 onward, including unpatched SE 21 and SE 25 builds.
-
Its x86-64 host or virtual machine exposes the
avx512vbmiCPU feature to Java. -
The running JVM has Base64 intrinsics enabled and has not been limited to AVX2 with
-XX:UseAVX=2.
On the WildFly host or virtual machine, check the CPU feature:
grep -m1 '^flags' /proc/cpuinfo | grep -qw avx512vbmi && echo 'AVX-512 VBMI available'
If this prints nothing, that CPU does not expose AVX-512 VBMI and is not known to be affected by this flaw. On a container platform, run the check on the node that executes the WildFly container.
Mitigation
If you are not using an image provided by WildFly, update your Java SE installation as soon as a patched update is available. Updates are available for many Java SE variants.
Update your WildFly-provided image as soon as we provide a patched release.
Until you have a patched Java SE available, start each affected JVM with the -XX:-UseBASE64Intrinsics flag. This is Red Hat’s preferred interim mitigation. It disables the vulnerable accelerated Base64 path while retaining other AVX-512 optimizations.
Bare metal or virtualized installations
In a non-containerized WildFly installation, the simplest way to set the -XX:-UseBASE64Intrinsics flag is by setting the JDK_JAVA_OPTIONS environment variable.
export JDK_JAVA_OPTIONS="-XX:-UseBASE64Intrinsics"
$JBOSS_HOME/bin/standalone.sh
Another option is to edit the JAVA_OPTS settings in the bin/standalone.conf or bin/domain.conf files (or, for Windows users, the .bat or .ps1 variants).
Docker/Podman installations
For users of our wildfly or wildfly-ee-10 container images, a simple way to add the flag is by setting JDK_JAVA_OPTIONS in your Dockerfile or Containerfile:
FROM quay.io/wildfly/wildfly
ENV JDK_JAVA_OPTIONS="-XX:-UseBASE64Intrinsics"
Or, you could set the environment variable when you start the container:
podman run -e JDK_JAVA_OPTIONS=-XX:-UseBASE64Intrinsics ....
Finally, you could also create an edited copy of our bin/standalone.conf file and copy it to your image’s Dockerfile or Containerfile:
FROM quay.io/wildfly/wildfly
COPY standalone.conf $JBOSS_HOME/bin/
If you use the wildfly-runtime image as the base image in your own Docker/Podman image you can also use any of the above approaches.
S2I
If you are using an image built using the wildfly-s2i builder, when you deploy set the JDK_JAVA_OPTIONS or the JAVA_OPTS_APPEND environment variable to -XX:-UseBASE64Intrinsics or add that flag to any existing setting.
By Brian Stansberry
| November 20, 2026