HighGHSA-5qcv-4rpc-jp93CVE-2026-35554

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

Published 7 Apr 2026 · Updated 10 Sept 2026

Is your project on an affected org.apache.kafka:kafka-clients?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2.8.0 <3.9.2
Fixed in
3.9.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.kafka:kafka-clients -DdepVersion=3.9.2 -DforceVersion=true
Affected
>=4.0.0 <4.0.2
Fixed in
4.0.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.kafka:kafka-clients -DdepVersion=4.0.2 -DforceVersion=true
Affected
>=4.1.0 <4.1.2
Fixed in
4.1.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.kafka:kafka-clients -DdepVersion=4.1.2 -DforceVersion=true

Details

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.

Is GHSA-5qcv-4rpc-jp93 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.kafka:kafka-clients, and gives you the command that fixes it.

More advisories for org.apache.kafka:kafka-clients

  • CriticalCVE-2026-33557Apache Kafka does not validate JWT tokens in its OAUTHBEARER authentication implementation · 20 Apr 2026
  • MediumCVE-2026-33558Apache Kafka exposes sensitive information in its DEBUG logs · 20 Apr 2026
  • MediumCVE-2025-27817Apache Kafka Client Arbitrary File Read and Server Side Request Forgery Vulnerability · 10 Jun 2025
  • MediumCVE-2024-31141Apache Kafka Clients: Privilege escalation to filesystem read-access via automatic ConfigProvider · 19 Nov 2024
  • MediumCVE-2017-12610Improper Authentication in Apache Kafka · 13 May 2022
  • MediumCVE-2021-38153Observable Discrepancy in Apache Kafka · 23 Sept 2021
org.apache.kafka:kafka-clients security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.