CVE-2026-76403: Splunk Connect for Kafka · The software does not validate, or incorrectly validates, a certificate.
Affects Splunk Connect for KafkaSource CVE Database V5
Not known to be exploited · CVSS 7.4 High : upgrade to 2.2.7 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% 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:H/I:H/A:NExploitation 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 16 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 and later. Users should upgrade to version 2.2.7 or newer to remediate this vulnerability. Until upgraded, users should consider the risk of data interception or alteration when using Kerberos authentication with HTTP Event Collector. No vendor advisory content was provided to indicate alternative mitigations or temporary fixes.
Description
CVE-2026-76403 is a vulnerability in Splunk Connect for Kafka versions 2.2 and from 2.2 up to but not including 2.2.7. It involves improper or missing validation of certificates when Kerberos authentication is used with the HTTP Event Collector in Splunk Enterprise. This flaw allows an unauthenticated attacker positioned in the network path to read or modify all relevant data sent from the connector. The issue arises because the Kerberos authentication path does not apply the configured certificate validation options when constructing the HTTP client.