<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Apache Kafka</title><link>https://kafka.apache.org/blog/security/</link><description>Recent content in Security on Apache Kafka</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://kafka.apache.org/blog/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Mitigating CVE-2026-114938 ("Java4Shell") in Apache Kafka deployments</title><link>https://kafka.apache.org/blog/2026/11/19/mitigating-cve-2026-114938-java4shell-in-apache-kafka-deployments/</link><pubDate>Thu, 19 Nov 2026 00:00:00 +0000</pubDate><guid>https://kafka.apache.org/blog/2026/11/19/mitigating-cve-2026-114938-java4shell-in-apache-kafka-deployments/</guid><description>CVE-2026-114938, also known as &amp;ldquo;Java4Shell&amp;rdquo;, is a vulnerability in the JDK that can affect Apache Kafka® deployments. The flaw is in an AVX-512 VBMI intrinsic that OpenJDK uses on x86-64 CPUs to speed up Base64 decoding.
Because the vulnerability is in the JDK, Kafka itself needs no upgrade or code change. The fix is to upgrade your JDK. Until you can, a JVM flag disables the affected code.
Who is affected A Kafka process (a broker, controller, Kafka Connect worker, Kafka Streams application or client) is affected only if both of these are true:</description></item></channel></rss>