Denial of Service (DoS) through the REST API in Splunk Connect for Kafka
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-400.
Summary
In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Representational State Transfer (REST) API and influence responses from a Hypertext Transfer Protocol (HTTP) Event Collector endpoint in Splunk Enterprise could cause the connector to retry failed event batches until event delivery stops. The vulnerability is possible because HTTP Event Collector delivery retry handling uses an unbounded default for failed batches instead of a finite retry limit. For more information see Install Splunk Connect for Kafka (https://help.splunk.com/en/data-management/integrate-data-with-add-ons/splunk-connect-for-kafka/2.2/install/install-splunk-connect-for-kafka), Data ingestion parameters for Splunk Connect for Kafka (https://help.splunk.com/en/data-management/integrate-data-with-add-ons/splunk-connect-for-kafka/2.2/overview/data-ingestion-parameters-for-splunk-connect-for-kafka), and Set up and use HTTP Event Collector with configuration files (https://help.splunk.com/en/splunk-enterprise/get-data-in/get-started-with-getting-data-in/9.4/get-data-with-http-event-collector/set-up-and-use-http-event-collector-with-configuration-files) in the Splunk documentation.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA Splunk Connect for Kafka (Splunk) Fixed in 2.2.7
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Splunk Connect for Kafka 2.2.7
4 records Highest priority Priority MEDIUM 1 MEDIUM, 3 LOW
Other records, highest priority first
- TI-2026-53457 Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for KafkaPriority MEDIUM 42
- TI-2026-53458 Improper Certificate Validation through HTTP Event Collector Kerberos Authentication in Splunk Connect for KafkaPriority LOW 34
- TI-2026-53456 Regular Expression Denial of Service (DoS) through the REST API in Splunk Connect for KafkaPriority LOW 27
Timeline
- 2026-10-02 Threatist record created from CVE-2026-76400
- 2026-10-03 Alias added: GHSA-hrxg-3jgf-4mh5
References
More Splunk Connect For Kafka vulnerabilities
- TI-2026-53457 Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for Kafka CVSS 3.1HIGH 8.2
- TI-2026-53458 Improper Certificate Validation through HTTP Event Collector Kerberos Authentication in Splunk Connect for Kafka CVSS 3.1HIGH 7.4
- TI-2026-53456 Regular Expression Denial of Service (DoS) through the REST API in Splunk Connect for Kafka CVSS 3.1MEDIUM 5.9
Sources
- CVE-2026-76400 · CVE Program
- CVE-2026-76400 · NVD
- FIRST EPSS
- GHSA-hrxg-3jgf-4mh5 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences