Java SE and OpenJDK flaw in Base64 decoding can lead to unauthenticated remote code execution
Oracle and the OpenJDK project released fixes on 17 November 2026 for CVE-2026-114938, a memory corruption bug that causes denial of service and, in some cases, unauthenticated remote code execution. Organisations running Java SE, OpenJDK, GraalVM or a downstream build on recent x86-64 servers are concerned, especially for internet-facing applications.
What to do now
- Product
- Oracle Java SE / OpenJDK
- Affected versions
- Java SE 8u511-perf; Java SE/OpenJDK 17.0.6 to 17.0.21, 21.0.13 and earlier, 25.0.5 and earlier, 27.0.1 and earlier; GraalVM for JDK 17 and 21
- Fixed in
- 8u513, 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1; GraalVM: refer to the vendor
- CVE
- CVE-2026-114938
CERT-EU advisory 2026-021 describes a high severity vulnerability in Java SE and OpenJDK tracked as CVE-2026-114938. Oracle and the OpenJDK project shipped fixes on 17 November 2026. The bug is a memory corruption issue that leads to denial of service and, in some cases, lets an unauthenticated attacker run code remotely.
The flaw sits in the JVM's Base64 intrinsic, the CPU-optimised path used to decode Base64. Exploitation depends on three conditions. The JVM must run on an x86-64 processor with avx512f, avx512bw, avx512vbmi and bmi2, which means Intel Xeon Ice Lake or later, or AMD Zen 4 or later. The intrinsic must be enabled, which is the default whenever the CPU supports those features. And attacker-controlled Base64 data must reach the decoder. ARM64 systems are not affected.
That last condition is easy to meet in web applications. The advisory lists HTTP Basic authentication, JWTs, SAML messages, cookies and TLS data as possible paths. CERT-EU notes that the affected runtimes underpin many well-known applications, including Keycloak, some Atlassian products and JFrog Artifactory.
Affected releases are Oracle Java SE 8 performance build 8u511-perf, Java SE and OpenJDK 17 from 17.0.6 to 17.0.21, 21 up to 21.0.13, 25 up to 25.0.5 and 27 up to 27.0.1, plus Oracle GraalVM for JDK 17 and 21. The fixed versions are 8u513, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 respectively; for GraalVM the advisory points to the vendor. OpenJDK-based distributions are also affected, among them Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, BellSoft Liberica, SAP SapMachine and Red Hat build of OpenJDK, each releasing fixes on its own schedule. Software that ships its own Java runtime remains exposed until its vendor provides an update.
CERT-EU advises updating, starting with internet-facing applications, and restarting every JVM afterwards. Where an immediate update is not possible, the intrinsic can be turned off with -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics. Alternatively, AVX-512 can be disabled with -XX:UseAVX=2, which may reduce performance. Both options require a JVM restart, and running java -XX:+PrintFlagsFinal -version | grep UseBASE64Intrinsics confirms the active setting.
What to do now
- Identify JVMs running on AVX-512 capable x86-64 hosts (Intel Ice Lake or later, AMD Zen 4 or later), starting with internet-facing services.
- Update to Java SE 8u513, 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1 depending on your branch, or to your OpenJDK distribution's fixed build, then restart all JVMs.
- If you cannot update right away, start the JVM with -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics (or -XX:UseAVX=2), restart, and confirm with java -XX:+PrintFlagsFinal -version | grep UseBASE64Intrinsics.
- Ask vendors of applications that bundle their own Java runtime, such as Keycloak, some Atlassian products or JFrog Artifactory, when they will ship a fixed version.