Webswing deployments can be affected. Update Java and restart each affected process.
Java4Shell (CVE-2026-114938) is a vulnerability in Java’s accelerated Base64 decoder, disclosed on November 17, 2026. Webswing deployments can be affected. Our source review confirmed that some Webswing Server and Admin Console requests reach the affected decoder before Webswing checks credentials or permissions. On a vulnerable Java runtime, this can cause a JVM crash or allow remote code execution with the privileges of the Webswing process. Red Hat security bulletin
Which deployments are affected?
The vulnerable HotSpot code path requires an unpatched Java build and an x86-64 CPU that exposes AVX-512 VBMI to the JVM. OpenJDK releases relevant to Webswing include Java 17 starting at 17.0.6, Java 21, and Java 25 before their respective fixes. Standard OpenJDK 8 and 11 builds and ARM64 are outside the affected HotSpot path. Check your Java vendor’s advisory for specialized builds, including Oracle Java 8 Enterprise Performance Pack. CERT-EU advisory · Oracle advisory
Check the Java runtime used by each Webswing process. Start with internet-facing Server and Admin instances, then check Session Pool and desktop application processes. A desktop application can use a different Java installation from the server, as configured by its jreExecutable setting. Webswing application configuration
How to protect your deployment
- Update Java and restart each affected process. Install a build your Java vendor confirms fixes CVE-2026-114938. After restarting, verify the build in the running process with
jcmd <pid> VM.version. Adoptium update guidance - If you need more time to patch, disable the affected optimization. Append
-XX:-UseBASE64Intrinsicsto the startup options of each affected HotSpot JVM and restart it. For desktop applications launched by Webswing, append the flag to the application’svmArgssetting and restart the affected application processes. Red Hat mitigation guidance · Webswing application configuration - Verify the temporary mitigation. Run
jcmd <pid> VM.flags -alland confirm that the running JVM reportsUseBASE64Intrinsics = false. Remove the temporary flag after installing the vendor’s fix. Red Hat verification guidance
