How To

Mitigating CVE-2026-114938 (Java4Shell) in Flow Director

Published

CVE-2026-114938, known as "Java4Shell", is a heap overflow in the JDK. It sits in an AVX-512 VBMI intrinsic that HotSpot uses on x86-64 CPUs to speed up Base64 decoding (java.util.Base64.getDecoder() / getUrlDecoder()). The flaw is in the JDK, not in Flow Director, so the permanent fix is a JDK that contains the fix. Until then, the intrinsic can be switched off with the JVM flag -XX:-UseBASE64Intrinsics.

Flow Director 6.1.1 already includes this mitigation. Its start scripts startserver and startserver.bat pass -XX:-UseBASE64Intrinsics to the JVM by default. This covers startflight and the Docker image as well, because both start the server through startserver. Nothing needs to be configured after upgrading.

Flow Director runs its SwiftMQ Router inside its own JVM. The mitigation in the SwiftMQ 13.2.7 start scripts therefore does not reach Flow Director; Flow Director's own start scripts need the flag, which is what 6.1.1 adds. A separate SwiftMQ Router that Flow Director connects to (for example with startflight) runs in its own JVM and needs its own mitigation, see Mitigating CVE-2026-114938 (Java4Shell) in SwiftMQ.

Who is affected

A Flow Director server is affected if both of these apply:

  • It runs on an affected JDK (see the table below).

  • It runs on an x86-64 CPU that supports AVX-512 VBMI.

ARM64 machines are not affected. That includes the linux aarch64 and macos aarch64 bundles and Docker on arm64. Java 8 and Java 11 are not affected either.

The Flow Director 6.0.x and 6.1.0 bundles ship GraalVM CE 25.4.4.1.1 (JDK 25.0.4.1.1), which is affected. So does the Docker image flowdirector/fdserver, which is based on ghcr.io/graalvm/graalvm-community:25i4-25.0.4.1.1. This makes the linux x64 and windows x64 bundles and the Docker image on amd64 affected on CPUs with AVX-512 VBMI.

Java

Affected

Fixed in

17

17.0.6 – 17.0.21

17.0.21.1

21

21 – 21.0.13

21.0.13.1

25

25 – 25.0.5

25.0.5.1

27

27 – 27.0.1

27.0.1.1

18 – 20, 22 – 24, 26

all releases

no fix

To check whether a Linux machine's CPU supports AVX-512 VBMI (no output means it does not):

Bash
grep -o -m1 avx512vbmi /proc/cpuinfo

To check the JDK version of a Flow Director bundle, run this in the installation directory:

Bash
# Linux
graalvm-jdk/bin/java -version

# macOS
graalvm-jdk/Contents/Home/bin/java -version

# Windows
graalvm-jdk\bin\java -version

Upgrading

Upgrade to Flow Director 6.1.1, available from flowdirector.io and as the Docker image flowdirector/fdserver:6.1.1. It still bundles GraalVM CE 25.4.4.1.1, because no fixed GraalVM CE release exists yet, but its start scripts disable the Base64 intrinsic, which removes the vulnerable code path. Flow Director 6.1.1 is built on SwiftMQ CE 13.2.7.

If you maintain your own copies of the start scripts, the upgrade does not change them. Add -XX:-UseBASE64Intrinsics to them yourself, or use the environment variable below.

Until you can upgrade

Disable the intrinsic with the JVM flag -XX:-UseBASE64Intrinsics. The start scripts pass the content of the environment variable FD_JVM_OPTIONS to the JVM, so no file has to be changed. The heap size is set separately with FD_HEAP and is not affected.

Linux and macOS

Bash
export FD_JVM_OPTIONS="-XX:-UseBASE64Intrinsics"
./startserver

If FD_JVM_OPTIONS is already set, append the flag to its existing value instead of replacing it.

If Flow Director runs as a systemd service, set the variable in the unit file and restart the service:

[Service]
Environment=FD_JVM_OPTIONS=-XX:-UseBASE64Intrinsics

Windows

set FD_JVM_OPTIONS=-XX:-UseBASE64Intrinsics
startserver.bat

Docker

The Docker image starts the server with the same startserver script, so FD_JVM_OPTIONS works there too. To check the JDK of an image:

Bash
docker run --rm --entrypoint java flowdirector/fdserver:6.1.0 -version

To apply the workaround:

Bash
docker run -e FD_JVM_OPTIONS=-XX:-UseBASE64Intrinsics flowdirector/fdserver:6.1.0

With Docker Compose:

YAML
services:
  flowdirector:
    image: flowdirector/fdserver:6.1.0
    environment:
      FD_JVM_OPTIONS: "-XX:-UseBASE64Intrinsics"

Notes

  • The flag is safe on every platform, including ARM64, where it simply has no effect. Do not use -XX:UseAVX=2 as an alternative: ARM64 JVMs refuse to start with it.

  • The same variable works with startflight / startflight.bat, which start the server through startserver.

Verifying the mitigation

Check the flag on the running server. Find its process id with jcmd -l (the main class is io.flowdirector.Launcher), then:

Bash
jcmd <pid> VM.flags -all | grep UseBASE64Intrinsics

The mitigation is active if the output shows false:

bool UseBASE64Intrinsics = false {product} {command line}

In Docker, look up the process id inside the container first:

Bash
docker exec <container> jcmd -l
docker exec <container> jcmd <pid> VM.flags -all | grep UseBASE64Intrinsics