Informational
Advisory: OpenJDK Base64 Vulnerability - Java4Shell (CVE-2026-114938)
CVE(S)
CVE-2026-114938
PRODUCT(S)
N/A
Updated
2026 Nov 18
Article Version
1
First Published
2026 Nov 18
Publication ID
sophos-sa-20261118-java4shell
Workaround
No
Overview
On November 17, 2026, a memory corruption vulnerability in the Base64 decoder of OpenJDK, CVE-2026-114938 (also referred to as “Java4Shell”), was publicly disclosed. Oracle rates it CVSS 3.1 8.1 (High); the researchers who reported it rate it CVSS 4.0 9.2 (Critical).
The flaw is in an optimised implementation of Base64 decoding that the Java runtime uses on x86-64 processors that support AVX-512 VBMI instructions. Where an application passes attacker-supplied data to the affected Base64 decoding functions, an unauthenticated remote attacker could corrupt Java heap memory, read sensitive data and potentially execute code. Systems on ARM64 processors, and x86-64 processors without AVX-512 VBMI support, are not affected.
OpenJDK 17.0.6 and later on the Java 17 line, and the Java 21, 25 and 27 lines, are affected across Java distributions. Sophos is not aware of any public reports of this vulnerability being exploited in the wild at this time.
Are Sophos products affected?
Sophos is investigating the impact of this vulnerability on its products and services. We will update this advisory as our investigation progresses.
General guidance for non-Sophos systems
The following guidance is for Java applications and systems that you manage yourself, such as servers and third-party products. It does not apply to Sophos products, which this advisory will cover as our investigation progresses.
Patching
Oracle released fixed Java SE builds on November 17, 2026, and other Java distributions are releasing updates. Apply your Java vendor’s update when it is available, and restart Java applications to load the patched runtime. Include Java runtimes bundled inside third-party products, and confirm patch status with those vendors.
Identifying affected systems
- Identify Java applications running on Java 17.0.6 or later, or on Java 21, 25 or 27, prioritising internet-facing applications.
- Check whether the host CPU supports AVX-512 VBMI. On Linux, the CPU flags include avx512vbmi.
- Prioritise applications that decode Base64 data received from untrusted sources, for example in authentication headers, tokens or file uploads.
Temporary mitigation
Neither Oracle nor the OpenJDK project has published a workaround. Third parties have described a JVM option as an interim measure: Calif, the researchers who reported the vulnerability, and Tenable report that starting the Java runtime with -XX:-UseBASE64Intrinsics disables the affected code. Sophos has not validated this option. Test it before deploying it, and treat it as a temporary measure only. Updating Java is the only fix for the vulnerability.
Related information
Sophos Responsible Disclosure Policy
To learn about Sophos security vulnerability disclosure policies and publications, see the Responsible Disclosure Policy.