Severity: Critical
CVE: CVE-2026-114938
Affected versions: WSE running on Eclipse Temurin 17, 21, 25, or 27, including the bundled Java runtime in WSE 4.8.28 and later.
What to do: Update to WSE 4.12.3. If you are not yet able to update your WSE version, apply the mitigation recommended below. Once Temurin releases a fix, you may also resolve this issue by updating Java.
Summary
A flaw in the Java runtime’s Base64 decoder (java.util.Base64.Decoder) on some x86-64 processors lets a remote client make the JVM write past the end of a memory buffer by sending crafted Base64 data. Depending on the application, this can lead to crashes, exposure of sensitive data, or remote code execution.
WSE runs on Eclipse Temurin, which hasn’t released a fix yet, so most WSE installations need the workaround until a patched Temurin version is available.
Am I affected?
You’re affected if both of the following are true:
- Your WSE server runs on Java 17 or later. This includes all WSE 4.9.0+ installations, new installations of WSE 4.8.28 (which bundle Java 21), and any earlier version you’ve configured to use Java 17 or later.
- Your WSE server has an x86-64 CPU with AVX-512 VBMI support, for example an Intel Xeon from Ice Lake onward or an AMD Zen 4 or newer processor. ARM64 servers aren’t affected.
To check the Java version that WSE uses, go to Server > About in WSE Manager. Or, if WSE uses its bundled runtime, run:
[install-dir]/java/bin/java -version
If you configured WSE to use a different runtime, run java -version from that runtime’s bin directory instead.
Mitigation
This workaround disables the vulnerable code path. Apply it to every affected server, including private servers that aren’t reachable from the internet, and plan to update WSE as soon as the patched version is released or update Java as soon as Temurin releases a fix.
1. Add the JVM option to WSE
Add -XX:-UseBASE64Intrinsics as a VMOption in [install-dir]/conf/Tune.xml, then restart WSE.
<!-- Inside <Tune> in Tune.xml -->
<VMOptions>
<!-- Keep your existing VMOption entries -->
<VMOption>-XX:-UseBASE64Intrinsics</VMOption>
</VMOptions>
Note: Upgrading WSE can replace
Tune.xml, so check that the option is still set after any upgrade.
For Docker deployments, set the JAVA_TOOL_OPTIONS environment variable to -XX:-UseBASE64Intrinsics on the WSE container. For example in the Docker Compose file:
environment: - JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics
2. Add the JVM option to WSE Manager
For standalone deployments, add the -XX:-UseBASE64Intrinsics as a VMOption to the WSE Manager launcher on your server.
For Docker deployments, set the JAVA_TOOL_OPTIONS environment variable to -XX:-UseBASE64Intrinsics on the WSE Manager container. For example in the Docker Compose file:
environment: - JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics
3. Confirm the option is active
After restarting, confirm that the running JVM uses the option:
jcmd [pid] VM.flags | grep UseBASE64Intrinsics
The output should include -XX:-UseBASE64Intrinsics.
You can also check the WSE logs for a line like this:
2026-11-18 14:42:22 UTC comment server INFO 200 - Java Args[0]: -XX:-UseBASE64Intrinsics
Resolution
Configure your WSE server to use a patched Java version or later. Oracle has released the fixed versions in the table below. Eclipse Temurin hasn’t released fixed versions yet; we’ll update this advisory when it does.
| Java version | Oracle | Eclipse Temurin |
|---|---|---|
| 17 | 17.0.21.1 | Not yet released |
| 21 | 21.0.13.1 | Not yet released |
| 25 | 25.0.5.1 | Not yet released |
| 27 | 27.0.1.1 | Not yet released |
Java versions 18 through 20, 22 through 24, and 26 are end-of-life and won’t receive fixes. If WSE uses one of these, move to a supported Java version.
Checking for signs of exploitation
No specific indicators of exploitation have been published. Unexpected JVM crashes can be a sign of attempted exploitation. Look for hs_err_pid*.log crash files and compare their timestamps with client connection events in the WSE access logs to identify related client IP addresses.
Disclosure timeline
- Nov 17, 2026: Oracle disclosed CVE-2026-114938 and released fixed Java versions.
- Nov 18, 2026: Wowza published this advisory and released WSE 4.12.3.




