Hi Masood,
CVE-2026-114938 is a JDK vulnerability, not a Kafka one. Exposure depends
on the JDK and hardware you run Kafka on, not on the Kafka version.
1. Kafka, like most Java applications, uses java.util.Base64. Treat any
Kafka process on an affected JDK and CPU as potentially affected.
2. Kafka configuration doesn't rule out exposure. Both of these must hold:
- Affected JDK: OpenJDK 17.0.6+, 21, 25 or 27 builds older than
17.0.21.1 / 21.0.13.1 / 25.0.5.1 / 27.0.1.1 (or your vendor's
equivalent). Java 8 and 11 are not listed as affected.
- x86-64 CPU with AVX-512 VBMI ("avx512vbmi" in /proc/cpuinfo).
ARM64 is not affected.
3. No Kafka release is affected in itself, and no Kafka upgrade is needed.
The exception is the apache/kafka Docker images, which bundle an
affected
Eclipse Temurin JRE. The apache/kafka-native images are not affected.
Until you can upgrade the JDK, the JVM option -XX:-UseBASE64Intrinsics
disables the affected code path. Set it through KAFKA_OPTS, including
for the Docker image (-e KAFKA_OPTS=-XX:-UseBASE64Intrinsics). We don't
expect a noticeable performance impact for Kafka. This workaround comes
from the researchers' write-up; it is not part of the Oracle/OpenJDK
advisories.
4. Yes. A fixed JDK on all Kafka JVMs is sufficient; no Kafka change is
needed.
We have posted the advisory here:
https://kafka.apache.org/blog/2026/11/19/mitigating-cve-2026-114938-java4shell-in-apache-kafka-deployments/
Thanks,
Manikumar
On Thu, Nov 19, 2026 at 10:40 AM Masood Khan <[email protected]> wrote:
> Hi Team,
> We are evaluating the impact of *CVE-2026-114938* (Java4Shell), an OpenJDK
> vulnerability involving the Base64 decoder. We are using Kafka version
> 3.9.2 APIs.
>
> Tenable's advisory identifies Apache Kafka Broker as potentially
> exploitable after authentication.
>
> Could you please help clarify the following?
>
> 1.
>
> Does Apache Kafka Broker use the affected OpenJDK Base64 decoder in an
> execution path that could make it vulnerable?
> 2.
>
> Is the reported exploitability applicable to standard Kafka broker
> deployments, or does it require specific configurations or conditions?
> 3.
>
> Are there any known affected Kafka versions or recommended Kafka-side
> mitigations?
> 4.
>
> Is upgrading to a fixed JDK build sufficient to address the
> vulnerability?
>
> We would appreciate your guidance so that we can accurately assess the
> impact on our Kafka implementation.
>
> Thanks
> Masood
>