CVE-2026-76402: The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. in Splunk Splunk Connect for Kafka
CVE-2026-76402 affects Splunk Connect for Kafka versions 2.2. An unauthenticated attacker with access to the Kafka Connect REST API can configure a non-secure HTTP Event Collector endpoint in Splunk Enterprise. This misconfiguration causes the connector to send authentication credentials to an attacker-controlled server, exposing sensitive credentials and allowing limited alteration of event delivery. The vulnerability arises because the HTTP Event Collector endpoint validation does not enforce secure transport by default.
AI Analysis
Technical Summary
In Splunk Connect for Kafka versions =2.2, an unauthenticated user able to access the Kafka Connect REST API can configure a non-secure HTTP Event Collector endpoint. This leads to the connector sending authentication credentials to an attacker-controlled server, resulting in credential exposure and limited event delivery manipulation. The root cause is insufficient validation of the HTTP Event Collector endpoint, which does not require secure transport by default.
Potential Impact
The vulnerability allows exposure of authentication credentials to an attacker-controlled server, compromising all relevant data sent through the connector. Additionally, the attacker can cause limited alteration of event delivery. There is no indication of impact on availability. The CVSS score of 8.2 (high) reflects the critical confidentiality impact with limited integrity impact and no availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the Kafka Connect REST API to trusted users only and avoid configuring non-secure HTTP Event Collector endpoints. Ensure that HTTP Event Collector endpoints require secure transport (HTTPS) to prevent credential exposure.
CVE-2026-76402: The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. in Splunk Splunk Connect for Kafka
Description
CVE-2026-76402 affects Splunk Connect for Kafka versions 2.2. An unauthenticated attacker with access to the Kafka Connect REST API can configure a non-secure HTTP Event Collector endpoint in Splunk Enterprise. This misconfiguration causes the connector to send authentication credentials to an attacker-controlled server, exposing sensitive credentials and allowing limited alteration of event delivery. The vulnerability arises because the HTTP Event Collector endpoint validation does not enforce secure transport by default.
CVSS v3.1
Score 8.2high
Affected software
pkg:maven/com.splunk/splunk-connect-for-kafkaRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Splunk Connect for Kafka versions =2.2, an unauthenticated user able to access the Kafka Connect REST API can configure a non-secure HTTP Event Collector endpoint. This leads to the connector sending authentication credentials to an attacker-controlled server, resulting in credential exposure and limited event delivery manipulation. The root cause is insufficient validation of the HTTP Event Collector endpoint, which does not require secure transport by default.
Potential Impact
The vulnerability allows exposure of authentication credentials to an attacker-controlled server, compromising all relevant data sent through the connector. Additionally, the attacker can cause limited alteration of event delivery. There is no indication of impact on availability. The CVSS score of 8.2 (high) reflects the critical confidentiality impact with limited integrity impact and no availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the Kafka Connect REST API to trusted users only and avoid configuring non-secure HTTP Event Collector endpoints. Ensure that HTTP Event Collector endpoints require secure transport (HTTPS) to prevent credential exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- cisco
- Date Reserved
- 2026-08-19T12:02:03.632Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a862261acd9273b49a704a1
Added to database: 08/19/2026, 21:38:41 UTC
Last enriched: 08/19/2026, 21:52:33 UTC
Last updated: 08/19/2026, 23:43:16 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.