Skip to main content
Mallory
HighVulnerability

CVE-2026-35554: Silent Cross-Topic Message Delivery in Apache Kafka Java Producer

Published Apr 7, 2026 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.7High · v3.1
EPSS0.45%40th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Apache Software Foundation
IdentifiersCVE-2026-35554CWE-362 · Concurrent Execution using Shared…

CVE-2026-35554 is a race condition in Apache Kafka Java producer client buffer pool management affecting kafka-clients versions 2.8.0–3.9.1, 4.0.0–4.0.1, and 4.1.0–4.1.1. When a produce batch expires because of delivery.timeout.ms while its network request remains in flight, its ByteBuffer is prematurely returned to the buffer pool. A subsequent batch can reuse and overwrite that buffer before the original request completes. If the batches target different topics, messages can be silently delivered to an unintended topic without an error being reported to the producer, compromising confidentiality and integrity.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Sensitive messages can reach consumers authorized to read an unintended destination topic but not the intended topic, undermining topic-level data isolation. Unexpected or incompatible messages can cause deserialization failures, processing errors, and corrupted downstream data. Silent delivery can prevent producers from detecting the misrouting through normal error handling. Arbitrary code execution and direct service unavailability are not established consequences of this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

No separate workaround or temporary mitigation is documented. Upgrade to a fixed client release rather than relying on unverified producer configuration changes.

Remediation

Patch, then assume compromise.

Upgrade the Apache Kafka Java client dependency to 3.9.2, 4.0.2, 4.1.2, 4.2.0, or a later fixed release appropriate to the deployed branch. Update applications and bundled dependencies that include vulnerable kafka-clients versions. For vendor-packaged integrations, apply the corresponding vendor security update containing the corrected client library.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationKafkaapplication
FAQ

Frequently asked questions

Is CVE-2026-35554 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-35554 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-35554?
As of Nov 6, 2026, Mallory has found no public exploit for CVE-2026-35554.
Is there a patch for CVE-2026-35554?
Upgrade the Apache Kafka Java client dependency to 3.9.2, 4.0.2, 4.1.2, 4.2.0, or a later fixed release appropriate to the deployed branch. Update applications and bundled dependencies that include vulnerable kafka-clients versions.
What products are affected by CVE-2026-35554?
Apache Software Foundation Kafka.
How severe is CVE-2026-35554?
CVE-2026-35554 has a CVSS v3.1 score of 8.7 (High) and an EPSS score of 0.45% (40th percentile) as of Nov 6, 2026.
Activity feed

Recent activity

9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 5, 2026Unity Linux 20.1050e / 20.1060e / 20.1070e Security Update: ka... | Tenable®A race condition in Apache Kafka Java producer clients prematurely returns a batch's ByteBuffer to the buffer pool when the batch expires while its network request remains in flight. Reuse of that buffer can corrupt message contents and silently deliver messages to unintended topics, exposing sensitive data to unauthorized consumers and disrupting downstream processing. The reference assigns a CVSS v3 base score of 8.7. Nessus detects affected installations using self-reported version information rather than testing the flaw.Read more ↗tenable cloud security pluginsNews · Oct 2, 2026Echo: org.apache.kafka:kafka-clients: security update to 3.9.2 | Tenable®A race condition prematurely returns a producer batch’s ByteBuffer to the buffer pool when the batch expires while its network request remains in flight. Reuse by another batch can corrupt message contents and silently deliver messages to unintended topics, exposing sensitive data and disrupting downstream processing. The advisory lists affected versions as ≤ 3.9.1, ≤ 4.0.1, and ≤ 4.1.1. Fixed releases include 3.9.2, 4.0.2, 4.1.2, and 4.2.0 or later. The reported CVSS v3 base score is 8.7 (High).Read more ↗redhat accessNews · May 14, 2026RHSA-2026:17668 - Security Advisory - Red Hat Customer PortalAn Apache Kafka Clients vulnerability causing information disclosure and data corruption due to a race condition in producer buffer management.Read more ↗redhat accessNews · May 5, 2026RHSA-2026:13631 - Security Advisory - Red Hat Customer PortalAn Apache Kafka Clients vulnerability causing information disclosure and data corruption due to a race condition in producer buffer management.Read more ↗
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.