Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for Kafka
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
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 could configure a non-secure Hypertext Transfer Protocol (HTTP) Event Collector endpoint in Splunk Enterprise that causes the connector to send authentication credentials to an attacker-controlled server, allowing for exposure of credentials that compromise all relevant data sent through the connector and limited alteration of event delivery. The vulnerability is possible because HTTP Event Collector endpoint validation does not require secure transport by default. 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
- Yes
- 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-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
- TI-2026-53455 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-76402
- 2026-10-03 Alias added: GHSA-mrh3-68v8-xhgq
References
More Splunk Connect For Kafka vulnerabilities
- 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
- TI-2026-53455 Denial of Service (DoS) through the REST API in Splunk Connect for Kafka CVSS 3.1MEDIUM 5.9
Sources
- CVE-2026-76402 · CVE Program
- CVE-2026-76402 · NVD
- FIRST EPSS
- GHSA-mrh3-68v8-xhgq · 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