On November 17, 2026, Calif disclosed Java4Shell (CVE-2026-114938), a memory corruption flaw in the Base64 decoder of OpenJDK 17 and later. It affects Java running on x86-64 CPUs with AVX-512 VBMI. ARM64 is not affected. Our November CSPU analysis covers the vulnerability in more detail.
What it means for Portal Dedicated
Portal Dedicated ships with its own Java runtime. That’s Java 25 in Portal Dedicated 6.14.0 and Java 21 in 6.12.0 and earlier. Both contain the affected code, so a Portal Dedicated server on an affected CPU runs a vulnerable Java runtime.
We are not aware of any exploitation of Java4Shell in Portal Dedicated, or of a way to exploit it there. We still recommend you fix it, because each of the options below is a small change.
What to do
You can fix it in any of these three ways:
- Start the Portal with the
-XX:-UseBASE64IntrinsicsJVM option, which turns off the affected code and works with the bundled Java. - Update the Java runtime in place. Install Java 25.0.5.1 or later for 6.14.0, or Java 21.0.13.1 or later for 6.12.0 and earlier, and point the Portal service at it.
- Upgrade to Portal Dedicated 6.14.1 or later. It bundles Java 25.0.5.1, which fixes Java4Shell.
We recommend the JVM option or updating the Java runtime in place. Portal Dedicated 6.15.0, with additional features, is coming soon.
The Portal Dedicated documentation has the steps for each option, and a one-line check for whether your server’s CPU is affected at all.
Portal SaaS
We have already updated Portal SaaS at portal.waratek.com to a fixed Java runtime. If you use Portal SaaS, you don’t need to do anything.
