CVE-2026-76401: Splunk Connect for Kafka · An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.
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
No explicit patch or remediation is provided in the input data. If you cannot patch yet, restrict unauthenticated access to the Kafka Connect REST API to trusted users only and avoid using untrusted regular expressions for timestamp extraction.
Description
CVE-2026-76401 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. An unauthenticated attacker who can access the Kafka Connect REST API can exploit this by configuring timestamp extraction with a crafted regular expression that causes inefficient processing. This leads to blocking of a Kafka Connect worker thread and stops event delivery for the affected connector. The root cause is that timestamp extraction evaluates user-supplied regular expressions without a time limit, allowing the worst-case computational complexity to be triggered.