[Security] OpenJDK "Java4Shell" vulnerability (CVE-2026-114938): mitigation applied to Snowplow-managed pipelines
Last updated: November 18, 2026
[18-Nov-2026]
A critical vulnerability in OpenJDK (Java 17.0.6 and later, including the Java 21 runtime our components use), known as Java4Shell, was disclosed this week: CVE-2026-114938 (NVD entry). It affects the optimised Base64 decoding built into the Java runtime, and could allow an unauthenticated attacker to execute code on an affected Java process.
We have had questions from several customers, so this notice sets out our position, the action we have taken, and what to expect from security scanners.
Is Snowplow affected?
Several components run on the affected Java runtime, and we have applied a mitigation to them. These include the Collector, Enrich, Iglu Server, our warehouse and lake loaders (including RDB Loader and transformer), the Bad Row Aggregator, Snowplow Micro and parts of Console.
The vulnerability can only be triggered on x86 CPUs that support the AVX-512 VBMI instruction set (Intel Ice Lake or newer, AMD Zen 4 or newer). ARM-based servers, such as AWS Graviton, are not affected. Because exposure depends on the underlying hardware, we are treating every Snowplow-managed pipeline as in scope.
Components that do not run on Java, such as Snowbridge, are not affected.
What have we done?
We have applied the mitigation recommended in the advisory across Snowplow-managed pipelines: the Java option -XX:-UseBASE64Intrinsics, which switches off the affected code path entirely. It was applied through rolling restarts, with no data loss reported.
Area | Status |
|---|---|
Collector | Mitigated |
Enrich | Mitigated |
Iglu Server (AWS, GCP, Azure) | Mitigated |
Warehouse and lake loaders (Snowflake, Databricks, BigQuery, Redshift, Lake Loader, S3, Postgres, Elasticsearch) | Mitigated |
RDB Loader and transformer | Mitigated |
Bad Row Aggregator | Mitigated |
Snowplow Micro | Mitigated |
Console and Data Quality | Mitigated |
Snowplow Mini | Being removed (18 Nov) |
The option has a small performance cost, which we are monitoring. We will remove it once patched images are rolled out.
What about Snowplow Mini?
Snowplow Mini reached end of life on 11 November 2026 and cannot receive this or any future fix, so we are removing remaining Mini instances from 18 November 2026. Customers with a live Mini have been contacted directly. Snowplow Micro is the replacement and is already mitigated. More details are in the Snowplow Mini sunset notice.
Do I need to do anything?
If Snowplow manages your pipeline: no. The mitigation has been applied by Snowplow, with no action needed on your side.
If you run Snowplow components in your own infrastructure: add the option to every Snowplow Java component (Collector, Enrich, Iglu Server, loaders, Bad Row Aggregator, Micro) until patched images are available. The simplest way is through an environment variable on each container:
JDK_JAVA_OPTIONS="<your existing options> -XX:-UseBASE64Intrinsics"On startup, each container logs a line beginning NOTE: Picked up JDK_JAVA_OPTIONS:. Check that it includes the option to confirm it was applied. If your hosts run on ARM, or on x86 CPUs without AVX-512 VBMI, the vulnerable path cannot be reached, but we still recommend applying the option.
We also suggest following the GitHub repositories for each component, or Docker Hub, to be notified when updated images are released.
A note for security scanners
The mitigation is a runtime setting. It does not change the Java version inside our images.
Security scanners identify this vulnerability by the Java runtime version, so they will continue to report CVE-2026-114938 on Snowplow images until patched images are released, even though the vulnerable code path is switched off. This is expected.
We will release updated images built on a patched Java 21 runtime once the upstream base image is published, and roll them out to Snowplow-managed pipelines as part of the managed service. We will update this notice when that happens.
Questions
If you have any questions, or your security team needs a formal response for a supplier assessment, please raise a ticket with Snowplow Support and reference this notice.