Security Bulletin 2026-11-20-01
Published: November 20, 2026 | Last updated: November 20, 2026
Abstract
A memory corruption vulnerability in the Java runtime's Base64 decoder (CVE-2026-114938, also known as Java4Shell) can allow remote code execution in Java applications running on certain Intel and AMD processors. The flaw is in the Java runtime, not in Dremio code. Dremio Software 26.1.14, an upcoming release, will include container images with a patched Java runtime. Until it is available, customers can apply the workaround described below. Dremio Cloud has been mitigated with no customer action required. For tarball and RPM installs, which use the host's Java runtime, customers must update Java themselves.
CVSS Qualitative Rating
- High
- CVSSv3.1
- Score: 8.1
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Java Runtimes
A Java process is vulnerable only when all of the following are true:
- Java version: 17.0.6 through 17.0.21, 21 through 21.0.13, or 25 through 25.0.5. Java 8, Java 11 and earlier Java 17 releases are not affected.
- Processor: x86-64 with AVX-512 VBMI support, such as Intel Xeon Ice Lake and later, and AMD EPYC Zen 4 and later. ARM64 processors and older x86 processors (for example Intel Skylake and Cascade Lake) are not affected.
- JVM setting:
UseBASE64Intrinsicsis enabled, which is the default.
Affected Releases
Dremio Software
- Container images (Kubernetes): Dremio Software 26.1.13 and earlier, and Helm chart 3.2.13 and earlier, are affected when they run on an affected processor. This includes Dremio's Open Catalog and OpenSearch images the Helm chart deploys. OpenSearch is exposed only inside the Kubernetes cluster, so it can be exploited only by workloads with network access to the OpenSearch service, not by clients outside the cluster.
- Tarball and RPM installs: These are affected only if the host's Java runtime is an affected version and the processor is affected.
Dremio Cloud
- Dremio Cloud: Dremio Cloud before the November 20, 2026 update.
Client Drivers and Connectors
- Java-based drivers (Arrow Flight SQL JDBC driver, ADBC driver for Java, Legacy JDBC driver): These run in the client's Java runtime and are affected only if that runtime and the client's processor are affected.
- Drivers and connectors that do not run on Java (Arrow Flight SQL ODBC driver, ADBC driver for Go): Not affected.
Current Mitigation Status
Dremio Software
- Container images (Kubernetes): The fix will be available in the upcoming 26.1.14 release. The images will use Java 21.0.13.1, or 17.0.21.1 for the
-jdk17image. Until then, apply the workaround described below. - Helm chart: The fix will be available in the upcoming 3.2.14 release, which updates the images it deploys to patched Java runtimes, including components that are not affected, such as ZooKeeper.
- Tarball and RPM installs: Dremio runs on the Java installed on the host, so the fix requires updating your Java runtime. Upgrading Dremio alone does not resolve the issue.
Dremio Cloud
- Addressed in the Dremio Cloud update on November 20, 2026.
Client Drivers and Connectors
- Java-based drivers: No Dremio fix is required. These drivers ship without a Java runtime and use the client's Java runtime instead.
Mitigation Guidance
Dremio Software
Kubernetes
- Apply the workaround below now. When Dremio Software 26.1.14 and Helm chart 3.2.14 are available, upgrade, then remove the workaround. Dremio Software 25.x is out of support and will not be fixed. If you are on 25.x, apply the workaround and plan an upgrade to a supported release.
- Workaround: Add the JVM option
-XX:-UseBASE64Intrinsicsto every affected Java process the chart deploys by updating your Helm chart values:- Set
JAVA_TOOL_OPTIONS=-XX:-UseBASE64IntrinsicsthroughextraEnvs,catalog.extraEnvsandcatalogservices.extraEnvs. - Add the flag to
opensearch.opensearchJavaOpts. - For Dremio's Open Catalog,
JAVA_TOOL_OPTIONSmust keep its existing logging flag, so set both in the same value:JAVA_TOOL_OPTIONS="-Djava.util.logging.manager=org.jboss.logmanager.LogManager -XX:-UseBASE64Intrinsics". - If you already set
coordinator.extraEnvs,executor.extraEnvsor an engine override, add the entry there as well. - Run
helm upgrade, then restart your engines.
- Set
Tarball and RPM
- Update the host Java runtime to 17.0.21.1, 21.0.13.1, 25.0.5.1, or a later update in the same release line (or your Java vendor's equivalent build), then restart Dremio.
- If you cannot update Java immediately, add the JVM option
-XX:-UseBASE64Intrinsics:- On every coordinator and executor, set
DREMIO_JAVA_SERVER_EXTRA_OPTS="-XX:-UseBASE64Intrinsics"inconf/dremio-env, appending to any existing value, then restart Dremio.
- On every coordinator and executor, set
Workaround impact
The -XX:-UseBASE64Intrinsics workaround switches Base64 decoding to the standard implementation. Results are unchanged, and any performance effect is limited to Base64 decoding. You can remove it after you upgrade Dremio or update Java.
Dremio Cloud
- No action is needed.
Client Drivers and Connectors
- Java-based drivers: Update the client's Java runtime to 17.0.21.1, 21.0.13.1, 25.0.5.1, or a later update in the same release line (or your Java vendor's equivalent build), then restart the client. This applies to both Dremio Software and Dremio Cloud users.
Verifying Protection
These checks cover Dremio Software deployments and Java-based client drivers. You don't need to check Dremio Cloud services.
- To check whether a node's processor is affected, run
grep -m1 -o -w avx512vbmi /proc/cpuinfo. No output means the processor is not affected, and no further checks are needed for that node. - Run
java -versionin each container, or on the host for tarball and RPM installs, as the user that runs Dremio. For Java-based client drivers, run it on the client machine. Your Java runtime is patched if it reports 17.0.21.1, 21.0.13.1, 25.0.5.1, or a later update in the same release line. - If you use the workaround, run
jcmd com.dremio.dac.daemon.DremioDaemon VM.flags -all | grep UseBASE64Intrinsicson an affected processor; the output must showUseBASE64Intrinsicsset tofalse. For Dremio's Open Catalog, which has nojcmd, the pod log must contain aPicked up JAVA_TOOL_OPTIONSline that includes the flag. For OpenSearch, the JVM arguments line in the startup log must include it.
References
Revision History
- November 20, 2026: Initial publication.