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

Summary

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.

Timeline

1. Apr 7, 2026, 1:07 PM UTCCVE published
2. Apr 7, 2026, 1:57 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Apr 7, 2026, 4:23 PM UTCRecord last updated

Affected versions

• org.apache.kafka:kafka-clients

  From 2.8.0 · through 3.9.1; From 4.0.0 · through 4.0.1; From 4.1.0 · through 4.1.1

• org.apache.kafka:kafka-clientsMaven

  From 2.8.0 · fixed in 3.9.2

• org.apache.kafka:kafka-clientsMaven

  From 4.0.0 · fixed in 4.0.2

• org.apache.kafka:kafka-clientsMaven

  From 4.1.0 · fixed in 4.1.2

References 2