Quick answers
- Is CVE-2026-76400 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76400 being exploited in the wild.
- How severe is CVE-2026-76400?
- Medium severity, with a CVSS score of 5.9, published 19 August 2026.
- Which products and versions are affected?
- Splunk Connect For Kafka below 2.2.7.
- Is there a fix for CVE-2026-76400?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-76400 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-76400?
- Check whether you run Splunk Connect For 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.
Technical details
The vulnerability is an unbounded retry mechanism (CWE-400) in the HTTP Event Collector delivery retry handling within Splunk Connect for Kafka versions below 2.2.7. An unauthenticated attacker with network access to the Kafka Connect REST API can craft requests that influence responses from the HTTP Event Collector endpoint, triggering continuous retry loops for failed event batches without a finite limit. The attack requires network reachability to the REST API and the ability to influence HTTP Event Collector responses. An attacker can achieve denial of service by exhausting connector resources and halting event delivery. The vulnerability is fixed in version 2.2.7 and later.
Affected products
- Splunk Connect for Kafka below 2.2.7
Timeline
- 2026-08-19: disclosed: CVE-2026-76400 published in SVD-2026-0808