Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-76402 – Credential Exposure via SSRF (Insecure HEC Endpoint) – Splunk Connect for Kafka 2.2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-76402 is a Server-Side Request Forgery (CWE-918) vulnerability in Splunk Connect for Kafka that allows an unauthenticated actor with access to the Kafka Connect REST API to configure an insecure HTTP Event Collector (HEC) endpoint. Because the connector does not enforce secure transport validation for the configured HEC endpoint by default, this can cause the connector to transmit Splunk authentication credentials (HEC tokens) to an attacker-controlled server. The issue carries a CVSS v3.1 base score of 8.2 (High).

Technical details

  • Root cause: The connector’s HTTP Event Collector endpoint validation logic does not require secure transport (e.g., TLS/HTTPS enforcement) by default when a connector configuration is applied.
  • Trigger conditions: An attacker who can reach the Kafka Connect REST API (which manages Splunk Connect for Kafka connector configurations) can submit or modify a connector configuration to point the HEC endpoint at a server they control.
  • Attack vector: Network — exploitation requires network access to the Kafka Connect REST API but does not require prior authentication to Splunk itself (PR:N, UI:N per the CVSS vector).
  • Impact: Once the malicious HEC endpoint is configured, the connector transmits HEC authentication credentials (tokens) to the attacker-controlled destination, resulting in high confidentiality impact (credential/token disclosure). The advisory also notes limited event delivery manipulation is possible (low integrity impact), while availability is not affected.

Affected software

  • Splunk Connect for Kafka versions 2.2 through 2.2.6 (fixed in 2.2.7)

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Splunk Connect for Kafka to version 2.2.7 or later, which enforces secure transport validation for HEC endpoint configuration.
  • If immediate patching is not possible:
    • Restrict network access to the Kafka Connect REST API to trusted administrative hosts only, since exploitation depends on reachability of this API.
    • Audit existing Kafka Connect connector configurations for Splunk Connect for Kafka to confirm the configured HEC endpoint uses HTTPS and points to a legitimate, expected Splunk HEC destination.
    • Rotate any HEC tokens that may have been exposed to an unexpected or attacker-controlled endpoint.
    • Apply network-layer egress controls to prevent the Kafka Connect host from sending outbound HEC traffic to unapproved destinations.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge