Quick answers
- Is CVE-2026-76402 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76402 being exploited in the wild.
- How severe is CVE-2026-76402?
- High severity, with a CVSS score of 8.2, published 19 August 2026.
- Which products and versions are affected?
- Splunk Connect For Kafka below 2.2.7.
- Is there a fix for CVE-2026-76402?
- A patch was published on 2026-08-19: Fixed in version 2.2.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76402 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-76402?
- Check whether you run Splunk Connect For Kafka at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a server-side request forgery (SSRF) vulnerability in Splunk Connect for Kafka versions below 2.2.7. An unauthenticated attacker with network access to the Kafka Connect REST API can configure the connector to use a non-secure HTTP endpoint for the Splunk HTTP Event Collector. Due to insufficient validation of the endpoint URL, the connector does not verify that the endpoint uses HTTPS and does not validate the certificate, allowing an attacker to intercept traffic and capture authentication credentials sent by the connector. An attacker can achieve credential theft, data exposure of all events sent through the connector, and limited manipulation of event delivery. The vulnerability is fixed in version 2.2.7 and later, where HTTPS is enforced by default and certificate validation is implemented.
Affected products
- Splunk Connect for Kafka below 2.2.7
Timeline
- 2026-08-19: disclosed
- 2026-08-19: patched: Fixed in version 2.2.7