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 version | Azul Zulu | Azul Platform Prime |
|---|---|---|
| 8 | Not affected | Affected |
| 11 | Not affected | Affected |
| 17 | Affected | Affected |
| 21 and later | Affected | Affected |
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:
grep -o 'avx512[a-z_]*' /proc/cpuinfo | sort -u
- If the command shows one or more
avx512features, 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 line | Fixed version |
|---|---|
| 26.08 | 26.08.110.0 |
| 26.02 | 26.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 version | Update type | Zulu version | JDK version |
|---|---|---|---|
| 27 | CSPU for PSU | 27.30.201 (CA) / 27.30.202 (SA) | 27.0.1.1+4 |
| 25 | CSPU for PSU | 25.38.201 (CA) / 25.38.202 (SA) | 25.0.5.1+2 |
| 25 | CSPU for CPU | 25.37.202 (SA) | 25.0.4.1.201+1 |
| 21 | CSPU for PSU | 21.54.201 (CA) / 21.54.202 (SA) | 21.0.13.1+2 |
| 21 | CSPU for CPU | 21.53.202 (SA) | 21.0.12.1.201+1 |
| 17 | CSPU for PSU | 17.70.201 (CA) / 17.70.202 (SA) | 17.0.21.1+2 |
| 17 | CSPU for CPU | 17.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
- Add
-XX:-UseBASE64Intrinsicsto the JVM command line. - If your application does very much Base64 encoding and decoding, use
-XX:UseAVX=2instead. Use one flag only. - Test the flag with a typical workload before you use it in production.
- 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.
- 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
| Flag | What it changes | Expected effect | Applications at risk |
|---|---|---|---|
-XX:-UseBASE64Intrinsics | Turns off only the optimized code for java.util.Base64 encode and decode | Base64 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=2 | Limits all vector instructions to AVX2 in all JIT-compiled code and intrinsics | Small 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
Article is closed for comments.