# CVE-2026-76402: Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for Kafka > Unauthenticated attackers can exploit SSRF in Splunk Connect for Kafka to steal credentials and compromise data delivery by configuring insecure HTTP endpoints. - **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 19 Aug 2026 - **Updated:** 20 Aug 2026 - **Also known as:** GHSA-mrh3-68v8-xhgq ## What is CVE-2026-76402? CVE-2026-76402 is a high-severity server-side request forgery vulnerability in Splunk Connect for Kafka, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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 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. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2026-76402? It affects 1 product. Products: Splunk Connect for Kafka. ## How do I fix CVE-2026-76402? No fix has been published for CVE-2026-76402 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-76402 being exploited? There is no known exploitation of CVE-2026-76402 in the wild and no public exploit code. ## Other vulnerabilities in Splunk Connect for Kafka - [CVE-2026-76403](https://insights.sbomify.com/CVE-2026-76403/): Improper Certificate Validation through HTTP Event Collector Kerberos Authentication in Splunk Connect for Kafka (high 7.4) - [CVE-2026-76400](https://insights.sbomify.com/CVE-2026-76400/): Denial of Service (DoS) through the REST API in Splunk Connect for Kafka (medium 5.9) - [CVE-2026-76401](https://insights.sbomify.com/CVE-2026-76401/): Regular Expression Denial of Service (DoS) through the REST API in Splunk Connect for Kafka (medium 5.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-76402 and fix it if it is affected. What it is: CVE-2026-76402 is a high-severity server-side request forgery vulnerability in Splunk Connect for Kafka, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-76402 in the wild and no public exploit code. Affected product: Splunk Connect for Kafka. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-76402/ (Markdown: https://insights.sbomify.com/CVE-2026-76402/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76402 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76402 - OSV: https://osv.dev/vulnerability/CVE-2026-76402 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-76402/ Summaries are generated and may contain mistakes; the official description above is the record.