How to Fix CVE-2026-35554: Use After Free in Apache Kafka Clients
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-27314: Apache Cassandra: Privilege escalation via ADD IDENTITY authorization bypass — Apache Cassandra: Privilege escalation via ADD IDENTITY authorization bypass
- How to Fix CVE-2026-41284: Denial of Service in Apache Tomcat — Denial of Service in Apache Tomcat
- How to Fix CVE-2026-42440: Memory Allocation with Excessive Size Value in Apache OpenNLP , Memory Allocation with Excessive Size Value in Apache OpenNLP
- How to Fix CVE-2026-33858: Deserialization of untrusted data in Apache Airflow , Deserialization of untrusted data in Apache Airflow
- How to Fix CVE-2026-34483: Encoding or escaping of output in Apache Tomcat , Encoding or escaping of output in Apache Tomcat
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
| Severity | CVSS 8.7, High |
|---|---|
| Actively exploited? | No |
| Affected | Apache Software Foundation Apache Kafka Clients (2.8.0 <= 3.9.1, 4.0.0 <= 4.0.1, 4.1.0 <= 4.1.1) |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-416: Use After Free |
CVE-2026-35554 is a use after free in Apache Software Foundation Apache Kafka Clients. The fix is to upgrade to see vendor advisory and apply the runnable commands below.
What is CVE-2026-35554?
A race condition in the Apache Kafka Java producer client’s buffer pool management can cause messages to be silently delivered to incorrect topics. When a produce batch expires due to delivery.timeout.ms while a network request containing that batch is still in flight, the batch’s ByteBuffer is prematurely deallocated and returned to the buffer pool. If a subsequent producer batch,potentially destined for a different topic,reuses this freed buffer before the original network request completes, the buffer contents may become corrupted.
In practical terms, a successful attacker gets untrusted deserialization that typically yields remote code execution. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.
Am I affected?
You are affected if you run Apache Software Foundation Apache Kafka Clients at a version listed in the Affected row above. Probe your installed build with the commands below.
# Confirm the installed version via your package manager
dpkg -l | grep -i apache # Debian/Ubuntu
rpm -qa | grep -i apache # RHEL/CentOS/Rocky
How to fix CVE-2026-35554
The primary fix is to upgrade to the patched build listed in the Fixed in row above (See vendor advisory). Pick the platform that matches your install and run the commands below.
Linux (Ubuntu / Debian)
# Vendor advisory: https://issues.apache.org/jira/browse/KAFKA-19012
sudo apt-get update
sudo apt-get install --only-upgrade apache-kafka-clients
# Confirm the installed version meets or exceeds <patched-version>
dpkg -s apache-kafka-clients | grep ^Version
Linux (RHEL / CentOS / Rocky)
sudo dnf upgrade --security apache-kafka-clients -y
rpm -q apache-kafka-clients
Windows (PowerShell, admin)
# Vendor advisory: https://issues.apache.org/jira/browse/KAFKA-19012
winget upgrade --id 'ApacheSoftwareFoundation.ApacheKafkaClients' --silent --accept-source-agreements --accept-package-agreements
# If winget doesn't know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\ApacheKafkaClients-<patched-version>.msi" -ArgumentList '/qn /norestart' -Wait
PowerShell script (Windows): detect, back up, upgrade, verify, log
# Vendor advisory: https://issues.apache.org/jira/browse/KAFKA-19012
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\ApacheKafkaClients-Patch-CVE-2026-35554.log"
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Tee-Object -FilePath $log -Append }
Write-Log "Starting CVE-2026-35554 remediation for Apache Software Foundation Apache Kafka Clients"
# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
Where-Object { $_.Name -like '*Apache*' } |
Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"
if (-not $installed) {
Write-Log "Product not installed on this host; nothing to do."
return
}
if ([version]$installed -ge [version]'<patched-version>') {
Write-Log "Already at fixed version $installed; no action needed."
return
}
# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\ApacheKafkaClients-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
$src = "$env:ProgramFiles\Apache Software Foundation\Apache Kafka Clients"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"
# 3. Apply the patched installer
$installer = "$env:TEMP\ApacheKafkaClients-<patched-version>.msi"
if (-not (Test-Path $installer)) {
throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"
# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
Where-Object { $_.Name -like '*Apache*' } |
Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'<patched-version>') {
Write-Log "SUCCESS: now at $verify (>= <patched-version>)"
} else {
Write-Log "FAILURE: still at $verify after install"
exit 1
}
Bash script (Linux): detect, back up, upgrade, verify, log
# Vendor advisory: https://issues.apache.org/jira/browse/KAFKA-19012
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/apache-kafka-clients-patch-cve-2026-35554.log
log() { echo "$(date -Iseconds) $*" | tee -a "$LOG"; }
log "Starting CVE-2026-35554 remediation for Apache Software Foundation Apache Kafka Clients"
# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s apache-kafka-clients >/dev/null 2>&1; then
CURRENT=$(dpkg-query -W -f='${Version}' apache-kafka-clients)
PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q apache-kafka-clients >/dev/null 2>&1; then
CURRENT=$(rpm -q --queryformat '%{VERSION}' apache-kafka-clients)
PKG_MGR=dnf
else
log "apache-kafka-clients not installed via apt or rpm; check your package manager or vendor instructions."
exit 0
fi
log "Detected: apache-kafka-clients=$CURRENT (manager=$PKG_MGR)"
# 2. Backup config
BACKUP=/var/backups/apache-kafka-clients-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/apache-kafka-clients /etc/${pkg%%-*} ; do
[ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done
# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
sudo apt-get update -y
sudo apt-get install --only-upgrade -y apache-kafka-clients
else
sudo dnf upgrade --security -y apache-kafka-clients
fi
# 4. Verify
if [ "$PKG_MGR" = apt ]; then
NEW=$(dpkg-query -W -f='${Version}' apache-kafka-clients)
else
NEW=$(rpm -q --queryformat '%{VERSION}' apache-kafka-clients)
fi
log "After upgrade: $NEW"
log "Done. Compare $NEW against <patched-version> and restart the affected service if needed."
If you cannot patch immediately
These are runnable hardening commands. They reduce blast radius but they are not a replacement for the vendor patch.
Rate-limit and log the affected endpoint at the reverse proxy
limit_req_zone $binary_remote_addr zone=admin:10m rate=10r/m;
location /<vulnerable-path> {
limit_req zone=admin burst=5 nodelay;
access_log /var/log/nginx/admin-access.log combined;
proxy_pass http://backend;
}
How to verify the fix worked
Run the version probe again and confirm the running build matches the Fixed in row above.
apache2 -v # Debian/Ubuntu
httpd -v # RHEL/CentOS
Expected output: the Server version line should show the patched build.
Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-35554 has cleared. Sweep your logs for indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.
Frequently asked questions
Is CVE-2026-35554 being actively exploited?
Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.
How severe is CVE-2026-35554?
CVSS rates it 8.7 (High). Use that score to set your patch priority alongside the other items in your queue.
Do I have to take Apache Kafka Clients offline to apply the patch?
It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.
What if my vulnerability scanner still flags CVE-2026-35554 after I patch?
Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.
References
- Official vendor advisory: https://issues.apache.org/jira/browse/KAFKA-19012
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-35554
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://lists.apache.org/thread/f07x7j8ovyqhjd1to25jsnqbm6wj01d6
*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Sourced from the official vendor advisory, the NVD record, and the CISA KEV listing. Always confirm against the vendor advisory before applying changes in production.*