Quick answers
- Is CVE-2026-83525 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-83525 being exploited in the wild.
- How severe is CVE-2026-83525?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- Apache Kafka 2.8.0 before 4.2.2, 4.3.0 before 4.3.2.
- Is there a fix for CVE-2026-83525?
- Yes: fixed in Kafka 4.2.2, 4.3.2, 4.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-83525 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-83525?
- Check whether you run Apache Kafka at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Kafka 4.2.2, 4.3.2, 4.4.0
Technical details
A logic error (CWE-480: incorrect comparison operator) in the FetchSnapshot RPC handler allows an authenticated attacker with CLUSTER_ACTION privilege to trigger controller process termination. The vulnerable code uses AND (&&) instead of OR (||) when validating that a FetchSnapshotRequest contains exactly one topic with one partition, allowing requests with empty topics arrays or topics with no partitions to bypass validation and cause a denial of service.
Affected products
- Apache Kafka 2.8.0 before 4.2.2, 4.3.0 before 4.3.2