Security Advisory: Java4Shell OpenJDK Base64 decoder vulnerability (CVE-2026-114938)

 

Date  Change 
2026-11-20  Initial publication. 

 

Key points for customers 

  • A new vulnerability has been disclosed in the OpenJDK Java runtime, known as Java4Shell (CVE-2026-114938). It affects the Java runtime behind some applications on the Instaclustr Managed Platform: Kafka® Connect, OpenSearch® 2.19.x and 3.x and, in one narrow case, Apache Kafka® 4.x. 
  • NetApp Instaclustr will be fixing Kafka Connect and OpenSearch by applying a configuration change that turns off the vulnerable decoder, then upgrading the Java runtime in our next scheduled patching cycle. The configuration change is currently being applied to affected instances and is expected to be completed by mid-January 2027.  
  • Apache Kafka brokers can only be exposed post authentication. We have assessed it as medium severity and will fix it in our next quarterly upgrade. We recommend reviewing users with access. 
  • You can reduce the risk associated to this vulnerability prior to the fix by reviewing your cluster firewall rules and ensuring that only the networks that need access are able to connect. 

Issue details 

Our ongoing CVE monitoring picked up a software vulnerability affecting the Java runtime on some Instaclustr managed nodes. 

OpenJDK Base64 decoder 

CVE-2026-114938 is a flaw in the optimised Base64 decoder built into OpenJDK on x86-64 processors that support AVX-512 VBMI (Intel Ice Lake or newer, AMD Zen 4 or newer). A crafted Base64 string can make the Java runtime write past the end of a memory buffer. Most often, the application simply crashes. The researchers who found it say that, with extra work tailored to each application, it could lead to remote code execution. There is no universal exploit, and we aren’t aware of any exploitation in the wild at the time of writing. 

A node is only exposed if all three of these are true: 

  • Java version: OpenJDK 17.0.6 or later, or Java 21, 25 or 27, without the fix. Oracle Java SE 8 Performance Pack builds (for example 8u511b33-perf) are also affected because they run the JDK 17 JVM. Standard Java 8 and Java 11 builds are not affected. 
  • Processor: the node runs on an x86-64 processor with AVX-512 VBMI. ARM64 nodes, including AWS Graviton, are not affected. 
  • Reachable decoder: the application decodes attacker-supplied data with the affected decoder. 

In Kafka Connect and OpenSearch 2.19.x and 3.x, the decoder handles the login header of a REST request before the password is checked. That means an attacker who can reach the REST port doesn’t need credentials to send the crafted data. Your cluster firewall rules limit who can connect to your nodes, which limits the attack surface to the addresses you allow. 

In Apache Kafka the only way to reach the decoder is through a dynamic SSL configuration change. That requires a Kafka user with ALTER_CONFIGS permission on the Cluster resource. No Kafka user has this permission by default; a customer administrator has to grant it. Unauthenticated callers and default Kafka users can’t reach the decoder. 

CVEs 

CVE  Public name  Area affected  Public CVSS v3.1 score  NetApp assessed score in the Instaclustr environment 
CVE-2026-114938  Java4Shell  The OpenJDK Base64 decoder on x86-64 processors with AVX-512 VBMI  8.1 (High)  OpenSearch 2.19.x and 3.x: 7.5 (High) 

Kafka Connect: 7.2 (High) 

Apache Kafka 4.x: 6.1 (Medium) 

All other applications: not affected 

 

Impact analysis 

We investigated this vulnerability and how it could affect Instaclustr Managed Platform customers, Enterprise Support customers, and NetApp Instaclustr’s own systems. No customer-facing NetApp Instaclustr systems, including the Console and APIs, are affected. 

Managed service customers 

These applications are affected when they run on nodes with an affected x86-64 processor: 

Application  Affected versions 
Kafka Connect  3.7.117, 3.9.0, 3.9.1, 3.9.2, 4.0.0, 4.1.1, 4.1.2, 4.2.1, 4.2.2, 4.3.1, 4.3.2 
OpenSearch  2.19.2, 2.19.3, 2.19.4, 2.19.5, 2.19.6, 3.5.0, 3.6.0, 3.9.0 
Apache Kafka (only with a user granted ALTER_CONFIGS on the Cluster resource)  4.1.1, 4.1.2, 4.2.1, 4.2.2, 4.3.1, 4.3.2 

 

Any applications that Instaclustr supports but are not listed above are not affected. 

NetApp Instaclustr will resolve this CVE by implementing the following activities: 

  • Applying a configuration change to all affected Kafka Connect and OpenSearch nodes that switches off the vulnerable decoder and removes the risk. Most affected nodes will receive this in our current patching round, and all by mid-January 2027. We will upgrade the Java runtime in our next scheduled patching cycle. 
  • For Apache Kafka, the next quarterly patching cycle will address this CVE. Once the upgrade is released, any new clusters will include it by default. 
  • If you run Apache Kafka and have given any Kafka user ALTER_CONFIGS on the Cluster resource, or removed the default deny rule for it, it’s worth checking whether that user still needs it. 

Enterprise Support customers 

  • Update your Java runtime to a fixed build and restart. Fixed versions include Oracle Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, and Amazon Corretto 17.0.21.1.2 and the matching 21, 25 and 27 builds. 
  • If you cannot update yet, add the JVM option -XX:-UseBASE64Intrinsics to affected applications and restart them. This turns off the vulnerable optimised decoder. For example, add it to cassandra-env.sh for Cassandra, kafka-env.sh for Kafka, or jvm.options for OpenSearch. 
  • Do not use -XX:UseAVX=2 as a mitigation in configuration shared with ARM64 nodes. ARM64 Java runtimes do not recognise this option and will fail to start. 
  • Applications that bundle their own Java runtime, such as OpenSearch, need their own update. At the time of writing, Eclipse Temurin had no confirmed fixed build. 
  • Restart processes after updating. Running processes keep the Java runtime they loaded at start. 

For the latest information on which version contains the fix, check your Java vendor’s security advisory (Oracle, Amazon Corretto, Eclipse Temurin, and others). 

If you have questions about this vulnerability, mitigations, or patching, please contact NetApp Instaclustr Support. Existing customers can also raise a ticket through the support portal. 

References