Denial of Service (DoS) through the REST API in Splunk Connect for Kafka
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Splunk | Splunk Connect for Kafka | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Splunk | Splunk Connect For Kafka |
|
Vendor Solution
Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status.
Vendor Workaround
Restrict access to the Kafka Connect Representational State Transfer (REST) API to trusted administrative hosts and networks. Set a finite HTTP Event Collector retry limit in the connector configuration. For more information see [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) in the Splunk documentation.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.381% probability within 30 days)
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-0808 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Splunk connect For Kafka
|
|
| CPEs | cpe:2.3:a:splunk:connect_for_kafka:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Splunk connect For Kafka
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Splunk
Splunk splunk Connect For Kafka |
|
| Vendors & Products |
Splunk
Splunk splunk Connect For Kafka |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Denial of Service (DoS) through the REST API in Splunk Connect for Kafka | |
| Weaknesses | CWE-400 | |
| References |
| |
| Metrics |
cvssV3_1
|