Java4Shell for Zulu and Zing (CVE-2026-114938)

CVE-2026-114938 (Java4Shell) affects Azul Zulu and Azul Platform Prime when the Base64 intrinsic uses an AVX-512 optimization on x86_64 CPUs. The November 2026 update, released on 17 November 2026, contains the fix. If you cannot upgrade now, a JVM flag stops the issue with no new installation.

Affected Java versions

Java versionAzul ZuluAzul Platform Prime
8Not affectedAffected
11Not affectedAffected
17AffectedAffected
21 and laterAffectedAffected

In OpenJDK, the issue comes from an AVX-512 Base64 optimization that was added in JDK 18 and backported to JDK 17. Azul Zulu 8 and Azul Zulu 11 do not contain this code.

In Azul Platform Prime, the Base64 intrinsic does not depend on the Java version. Thus, Azul Platform Prime is affected on all Java versions from Java 8.

Affected platforms

Only x86_64 systems with CPUs that support AVX-512 are affected. ARM64 systems are not affected, for example Apple Silicon macOS and Linux on ARM.

Check if your CPU is affected

On Linux x86_64, run this command on the host, VM, or container where the JVM runs:

 
bash
grep -o 'avx512[a-z_]*' /proc/cpuinfo | sort -u
  • If the command shows one or more avx512 features, the CPU supports AVX-512. The system is affected if it also runs an affected Java version.
  • If the command shows no output, the CPU does not support AVX-512. The system is not affected.

Fixed versions

Azul Platform Prime

Release lineFixed version
26.0826.08.110.0
26.0226.02.510.0

Each fixed version includes all Java versions that the release line supports. If you use an older version in a release line, upgrade to the fixed version in the same line.

No fix is available for unsupported release lines. If you use an unsupported version, use the workaround below, or upgrade to a supported release line.

Azul Zulu

Java versionUpdate typeZulu versionJDK version
27CSPU for PSU27.30.201 (CA) / 27.30.202 (SA)27.0.1.1+4
25CSPU for PSU25.38.201 (CA) / 25.38.202 (SA)25.0.5.1+2
25CSPU for CPU25.37.202 (SA)25.0.4.1.201+1
21CSPU for PSU21.54.201 (CA) / 21.54.202 (SA)21.0.13.1+2
21CSPU for CPU21.53.202 (SA)21.0.12.1.201+1
17CSPU for PSU17.70.201 (CA) / 17.70.202 (SA)17.0.21.1+2
17CSPU for CPU17.69.204 (SA)17.0.20.1.201+1

The fix has no performance cost. It corrects the AVX-512 Base64 intrinsic and keeps it on. After you install a fixed version, you do not need the workaround.

Workaround if you cannot upgrade now

  1. Add -XX:-UseBASE64Intrinsics to the JVM command line.
  2. If your application does very much Base64 encoding and decoding, use -XX:UseAVX=2 instead. Use one flag only.
  3. Test the flag with a typical workload before you use it in production.
  4. Optional (Azul Platform Prime only): you can set the flag as a JDK default, so that it applies on each new installation. Contact Azul Support for instructions.
  5. Plan an upgrade to a fixed version.

The -XX:-UseBASE64Intrinsics workaround also works on Azul Zulu and is recommended for other OpenJDK builds. For more information, see the Red Hat security bulletin.

Performance effect of the workaround flags

FlagWhat it changesExpected effectApplications at risk
-XX:-UseBASE64IntrinsicsTurns off only the optimized code for java.util.Base64 encode and decodeBase64 operations become slower, possibly much slower for big buffers. All other code stays the same.Applications that do much Base64 work (for example JSON or XML with encoded data, tokens, attachments)
-XX:UseAVX=2Limits all vector instructions to AVX2 in all JIT-compiled code and intrinsicsSmall for most applications. On some Intel CPUs, AVX-512 decreases the clock speed, so AVX2 can be equal or faster.Applications with many vector operations (array and string operations, some cryptography, auto-vectorized loops)

On CPUs without AVX-512, -XX:UseAVX=2 has no effect, but -XX:-UseBASE64Intrinsics still turns off the AVX2 Base64 code. Thus, it can have a small cost on CPUs that are not affected.

More information

If you have questions, contact Azul Support.

Add Comment

Comments

0 comments

Article is closed for comments.

Was this article helpful?
0 out of 0 found this helpful