CVE-2026-76400: Splunk Connect for Kafka · The software does not properly control the allocation and maintenance of a limited resource thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.
Affects Splunk Connect for KafkaSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 2.2.7 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.2.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Splunk Connect for Kafka to 2.2.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Connect for Kafka | Affected
| Fixed in
|
Mavencom.splunk/splunk-connect-for-kafkapkg:maven/com.splunk/splunk-connect-for-kafkaOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Splunk Connect for Kafka version 2.2.7. Users should upgrade to version 2.2.7 or later to address this issue. Until then, restricting access to the Kafka Connect REST API and controlling HTTP Event Collector endpoint responses can help mitigate exploitation risk.
Description
CVE-2026-76400 is a medium severity vulnerability in Splunk Connect for Kafka versions 2.2 and from 2.2 up to but not including 2.2.7. It allows an unauthenticated user who can access the Kafka Connect REST API and influence HTTP Event Collector responses to cause the connector to retry failed event batches indefinitely. This unbounded retry behavior can exhaust system resources, leading to denial of service conditions.