Published: November 18, 2026 8:45 PM PST
Last Updated: November 20, 2026 8:35 AM PST
On 17 November 2026, researchers publicly disclosed a vulnerability in the OpenJDK Base64 decoder, tracked as CVE-2026-114938 and nicknamed "Java4Shell". The vulnerability affects Java 17, 21 and 25 running on x86-64 processors with AVX-512 Vector Byte Manipulation Instructions (VBMI): Intel Ice Lake or newer, and AMD Zen 4 or newer. The researchers report that it can be used for remote code execution in some widely deployed Java applications. Technical details and demonstrations are public, so we recommend acting now.
Affected products
- Confluent Cloud (Confluent-managed services)
Confluent manages the Java runtime for Confluent Cloud. This issue has already been mitigated, and no further action is necessary. We have not seen any exploitation attempts of this vulnerability against our infrastructure or products.
- Confluent Platform (Customer-managed components)
Installed from packages or archives. These products use customer provided Java runtime. Per the OpenJDK vulnerability advisory, a runtime built from an OpenJDK version in the range below is affected. Check your vendor's security advisory for the specific fixed versions.
| Product | Affected versions | What to do |
| Confluent Platform 7.6.x to 8.4.x and Control Center 2.0.x to 2.7.x |
17.0.6 to below 17.0.21.1 21 to below 21.0.13.1 25 to below 25.0.5.1 |
Upgrade to your vendor's fixed build (see Remediation), within a Java version supported by Confluent Platform. |
Docker images. These ship their own Java runtime, so they are affected as published.
| Product | Affected versions | What to do |
| Confluent Manager for Apache Flink (CMF) | < 2.0.6, 2.1.6, 2.2.4, 2.3.4, 2.4.5, 2.5.1 | Upgrade (see Remediation). |
| Confluent Platform for Apache Flink (-java17 and -java21 tags) | <1.19.3-cp8, 1.20.5-cp4, 2.0.2-cp5, 2.1.3-cp4, 2.2.0-cp4, 2.3.0-cp2 | Upgrade, then redeploy your Flink jobs (see Remediation). |
| Confluent Platform for Apache Flink SQL image (CMF 2.5, Flink 2.3) | 2.3-cmf2.5-cp1 | Upgrade, then redeploy your Flink jobs (see Remediation). |
| Confluent Platform for Apache Flink Kubernetes Operator |
<1.12.1-cp4, 1.13.0-cp7, 1.14.0-cp5, 1.15.0-cp5, 1.16.1-cp2 Helm chart: |
Upgrade (see Remediation). |
| Confluent for Kubernetes (CFK) init container | <= 2.10.2, <= 2.11.2 and 3.0.0 | Upgrade (see Remediation). |
| Confluent Platform | <= 7.7.13-1-ubi8, 7.8.12-1-ubi8, 7.9.11-1-ubi8, 8.0.9-1-ubi9, 8.1.7-1-ubi9, 8.2.5-1-ubi9, 8.3.3-1-ubi9, 8.4.1-1-ubi9 | Upgrade (see Remediation). |
| Control Center | <= 2.0.01-ubi8, 2.1.0-1-ubi8, 2.2.2-1-ubi9, 2.3.2-1-ubi9, 2.4.2-1-ubi9, 2.5.1-1-ubi9, 2.6.1-1-ubi9, 2.7.0-1-ubi9 | Upgrade (see Remediation). End-of-life versions without a fix: apply the mitigation (see Mitigations). |
| Confluent Gateway | <= 1.0.0-1-ubi9, 1.1.2-1-ubi9, 1.2.2-1-ubi9, 1.3.1-1-ubi9, 1.4.0-1-ubi9 | Upgrade (see Remediation). End-of-life versions without a fix: apply the mitigation (see Mitigations). |
Recommended actions
Remediation
Upgrade to these versions or later. We will add the remaining Docker images as their fixed versions are released.
Installed from packages or archives. Upgrade the Java runtime to the fixed version as per your vendor's security advisory.
| Product | Fixed versions (OpenJDK baseline) |
| Confluent Platform 7.6.x to 8.4.x and Control Center 2.0.x to 2.7.x | OpenJDK 17.0.21.1, 21.0.13.1, 25.0.5.1 |
Docker images. For Confluent Platform, Control Center and Confluent Gateway, the amd64 images include the patched JDK. The arm64 images are unchanged because arm64 is not affected.
| Product | Fixed versions |
| Confluent Manager for Apache Flink (CMF) |
2.0.6, 2.1.6, 2.2.4, 2.3.4, 2.4.5, 2.5.1 Helm chart: same versions |
| Confluent Platform for Apache Flink (-java17 and -java21 tags) | 1.19.3-cp8, 1.20.5-cp4, 2.0.2-cp5, 2.1.3-cp4, 2.2.0-cp4, 2.3.0-cp2 |
| Confluent Platform for Apache Flink SQL image (CMF 2.5, Flink 2.3) | 2.3-cmf2.5-cp2 |
| Confluent Platform for Apache Flink Kubernetes Operator |
1.12.1-cp4, 1.13.0-cp7, 1.14.0-cp5, 1.15.0-cp5, 1.16.1-cp2 Helm chart: 1.121.4, 1.130.7, 1.140.5, 1.150.5, 1.161.2 |
| Confluent for Kubernetes (CFK) init container | 2.10.3, 2.11.3 and 3.0.1, or later |
| Confluent Platform | 7.7.13-2-ubi8, 7.8.12-2-ubi8, 7.9.11-2-ubi8, 8.0.9-2-ubi9, 8.1.7-2-ubi9, 8.2.5-2-ubi9, 8.3.3-2-ubi9, 8.4.1-2-ubi9 |
| Control Center | 2.6.1-2-ubi9, 2.7.0-2-ubi9 |
| Confluent Gateway | 1.2.2-2-ubi9, 1.3.1-2-ubi9, 1.4.0-2-ubi9 |
Mitigations
If a product has no fixed version yet, or you cannot upgrade, apply this mitigation:
- Add -XX:-UseBASE64Intrinsics to every affected Java process running Java 17, 21 or 25, and restart it. Add it only to those processes: on Java 8 the process will not start with this flag.
- Confirm the flag on each running process with jinfo -flag UseBASE64Intrinsics <pid>; The output must be -XX:-UseBASE64Intrinsics. Checking the command line is not enough, because a later option can undo the flag.
Where to set the flag:
| Component | Configuration |
|---|---|
| Kafka broker, KRaft controller, ZooKeeper, Connect, Replicator | KAFKA_OPTS |
| Schema Registry | SCHEMA_REGISTRY_OPTS |
| REST Proxy | KAFKAREST_OPTS |
| ksqlDB | KSQL_OPTS |
| Control Center (legacy and next-gen) | CONTROL_CENTER_OPTS |
| Confluent Gateway | GATEWAY_OPTS (CFK: spec.podTemplate.envVars) |
| Confluent for Kubernetes |
spec.configOverrides.jvm: ["-XX:-UseBASE64Intrinsics"] on every Confluent Platform custom resource:
|
| cp-ansible |
Each component's *_custom_java_args:
Rerun the playbook with *_skip_restarts: false. |
| Package installs (systemd) | The same per-component variable through Environment=, then restart. |
| Confluent Manager for Apache Flink, Confluent Platform for Apache Flink Kubernetes Operator and Flink jobs | See "Confluent Platform for Apache Flink" below. Do not use JAVA_TOOL_OPTIONS. |
If a variable is already set, append the flag at the end, separated by a space. Make sure nothing applied later re-enables it, such as -XX:+UseBASE64Intrinsics or _JAVA_OPTIONS.
Confluent Platform for Apache Flink
Add the flag in three places. Restarting Confluent Manager for Apache Flink or the operator does not restart running jobs, so redeploy every job afterwards.
-
Confluent Manager for Apache Flink: add the flag to the chart value jvmArgs, keeping existing arguments, and run helm upgrade with your current chart version. On version 2.5, if you customized cmf.statementService, also add the flag to:
- Any sharedCompilers entry that sets its own jvmArgs, and
- Both workers.jvmArgs and workers.compilerJvmArgs. Setting a worker value replaces its default, so keep a heap size in it.
- Kubernetes Operator: add the flag to jvmArgs.operator and jvmArgs.webhook. Under defaultConfiguration.flink-conf.yaml, set kubernetes.operator.default-configuration.flink-version.v1_19+.env.java.default-opts.jobmanager and .taskmanager to the flag. On chart 1.16 or later, use config.yaml instead if your values already set it. Do not use default-opts.all. Run helm upgrade, then restart the operator deployment.
-
Flink jobs: redeploy every job.
- Applications and FlinkDeployments: change spec.restartNonce.
- SQL statements on a dedicated compute pool: stop and resume each statement.
- SQL statements on a shared compute pool: stop the statements, change spec.clusterSpec.restartNonce, and resume them once the pool is running.
- FlinkSessionJobs: redeploy the session cluster.
If a job sets its own env.java.default-opts.jobmanager or .taskmanager, add the flag to the end of that value. If a job sets -XX:+UseBASE64Intrinsics in env.java.opts.*, remove it.
To confirm, check that the last UseBASE64Intrinsics option on each running Confluent Manager for Apache Flink, operator, webhook, compiler, JobManager and TaskManager process is -XX:-UseBASE64Intrinsics. For version 2.5 compile workers, check that SP_JVM_OPTS and SP_COMPILER_JVM_OPTS in the pod spec contain the flag.
Performance
The -XX:-UseBASE64Intrinsics flag turns off the hardware-accelerated Base64 routine for both encoding and decoding, and Java uses its standard implementation instead. Base64 results are identical. The flag disables the hardware-accelerated code for both encoding and decoding, which may affect performance depending on your workload. We recommend testing to understand any performance impact in your environment.
Support
For help, open a case on the Confluent Support Portal and reference CVE-2026-114938 or Java4Shell.
Revision Log
| Date | Status Update |
| 11/18/2026 | Published. |
| 11/19/2026 | Clarified impacted versions and added upgrade guidance for the Confluent for Kubernetes (CFK) init container and fixed versions for Confluent Platform for Apache Flink. |
| 11/20/2026 | Added fixed versions for Confluent Platform, Control Center and Gateway images. |
| 11/20/2026 | Updated affected and fixed image tags for Confluent Platform, Control Center and Confluent Gateway. |