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 SwiftMQ, 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.
SwiftMQ 13.2.7 already includes this mitigation. Its start scripts router and router.bat pass -XX:-UseBASE64Intrinsics to the JVM by default. This applies to SwiftMQ CE, UR and HA, and to the Docker images. Nothing needs to be configured after upgrading.
Who is affected
A SwiftMQ Router 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 SwiftMQ bundles up to and including 13.2.6 ship GraalVM CE 25.4.4.1.1 (JDK 25.0.4.1.1), which is affected. So are the Docker images, which are 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 images 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):
grep -o -m1 avx512vbmi /proc/cpuinfo
To check the JDK version of a SwiftMQ bundle, run this in the installation directory:
# Linux
graalvm-jdk/bin/java -version
# macOS
graalvm-jdk/Contents/Home/bin/java -version
# Windows
graalvm-jdk\bin\java -version
Upgrading
Upgrade to SwiftMQ 13.2.7. 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.
If you run SwiftMQ on your own JDK instead of the bundled one, upgrade that JDK to a fixed version from the table above.
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 variables below.
Until you can upgrade
Disable the intrinsic with the JVM flag -XX:-UseBASE64Intrinsics. The start scripts read it from an environment variable, so no file has to be changed.
Linux and macOS
The router script appends the content of SWIFTMQ_JVMOPENS to the JVM options:
export SWIFTMQ_JVMOPENS="-XX:-UseBASE64Intrinsics"
./router
If SWIFTMQ_JVMOPENS is already set, append the flag to its existing value instead of replacing it.
If the router runs as a systemd service, set the variable in the unit file and restart the service:
[Service]
Environment=SWIFTMQ_JVMOPENS=-XX:-UseBASE64Intrinsics
Windows
router.bat does not read SWIFTMQ_JVMOPENS. Use SWIFTMQ_JVMPARAM instead:
set SWIFTMQ_JVMPARAM=-Xmx2G -XX:-UseBASE64Intrinsics
router.bat
SWIFTMQ_JVMPARAM replaces the default JVM parameters (-Xmx2G). Always repeat your heap size together with the flag, otherwise the router starts with the JVM's default heap.
Docker
The Docker images start the router with the same router script, so SWIFTMQ_JVMOPENS works there too. To check the JDK of an image:
docker run --rm --entrypoint java iitsoftware/swiftmq-ce:13.2.6 -version
To apply the workaround:
docker run -e SWIFTMQ_JVMOPENS=-XX:-UseBASE64Intrinsics iitsoftware/swiftmq-ce:13.2.6
With Docker Compose:
services:
swiftmq:
image: iitsoftware/swiftmq-ce:13.2.6
environment:
SWIFTMQ_JVMOPENS: "-XX:-UseBASE64Intrinsics"
Notes
-
The flag is safe on every platform, including ARM64, where it simply has no effect. Do not use
-XX:UseAVX=2as an alternative: ARM64 JVMs refuse to start with it. -
The flag works on Java 11 and later. Java 8 rejects it, but Java 8 is not affected.
-
SwiftMQ clients (JMS, AMQP, CLI) run on your own JVM, not on the router's. If they run on an affected JDK and CPU, add
-XX:-UseBASE64Intrinsicsto their Java command line too, or upgrade their JDK.
Verifying the mitigation
Check the flag on the running router. Find its process id with jcmd -l (the main class is com.swiftmq.Router, or com.swiftmq.HARouter for SwiftMQ HA), then:
jcmd <pid> VM.flags -all | grep UseBASE64Intrinsics
The mitigation is active if the output shows false:
bool UseBASE64Intrinsics = false {product} {command line}
In Docker, the router is process 1 of the container:
docker exec <container> jcmd 1 VM.flags -all | grep UseBASE64Intrinsics