CVE-2026-76402: Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for Kafka
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk Connect for Kafkato a version that resolves this vulnerability.Fixed in 2.2.7
Event History
Frequently Asked Questions
Which deployments are exposed?
Splunk Connect for Kafka versions below 2.2.7 are exposed when an unauthenticated user can reach the Kafka Connect REST API. The issue applies because HTTP Event Collector endpoint validation does not require secure transport by default.
What does an attacker need to exploit this issue?
An attacker needs network access to the Kafka Connect REST API; no authentication or user interaction is required. They can configure a non-secure HTTP Event Collector endpoint that points to an attacker-controlled server.
What is the likely impact of successful exploitation?
The connector can send authentication credentials to the attacker-controlled server. Those credentials may compromise all relevant data sent through the connector and permit limited alteration of event delivery.
How can teams determine whether they may already be affected?
Check whether Splunk Connect for Kafka is below version 2.2.7, whether its Kafka Connect REST API is reachable by unauthenticated users, and whether HTTP Event Collector endpoints can be configured without secure transport.
What can be done before upgrading?
Restrict unauthenticated access to the Kafka Connect REST API and avoid non-secure HTTP Event Collector endpoints. Require secure transport for endpoint configuration where possible.