CVE-2026-35554

Apache Kafka Clients: Kafka Producer Message Corruption and Misrouting via Buffer Pool Race Condition

HIGH
8.7
CVSS Score
Published: April 7, 2026 at 01:07 PM UTC
Updated: August 17, 2026 at 06:25 PM UTC
1 product affected across 1 vendorKafka

Using Apache Kafka Clients by Apache Software Foundation?

Get instant alerts when new vulnerabilities affect Apache Kafka Clients - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.7
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

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. This can result in messages being delivered to unintended topics without any error being reported to the producer. Data Confidentiality: Messages intended for one topic may be delivered to a different topic, potentially exposing sensitive data to consumers who have access to the destination topic but not the intended source topic. Data Integrity: Consumers on the receiving topic may encounter unexpected or incompatible messages, leading to deserialization failures, processing errors, and corrupted downstream data. This issue affects Apache Kafka versions ≤ 3.9.1, ≤ 4.0.1, and  ≤ 4.1.1. Kafka users are advised to upgrade to 3.9.2, 4.0.2, 4.1.2, 4.2.0, or later to address this vulnerability.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.8.0 ≤ v ≤ 3.9.12.8.0 ≤ v < 3.9.24.0.0 ≤ v ≤ 4.0.14.0.0 ≤ v < 4.0.24.1.0 ≤ v ≤ 4.1.14.1.0 ≤ v < 4.1.22.8.04.0.04.1.0
Affected range stops below 3.9.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

Mailing ListVendor Advisory
Source: cverecord
https://lists.apache.org/thread/f07x7j8ovyqhjd1to25jsnqbm6wj01d6
Mailing ListThird Party Advisory
Source: af854a3a-2127-422b-91ae-364da2661108
http://www.openwall.com/lists/oss-security/2026/04/07/6

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.7HIGHCISA-ADP
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-416CWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card