Read the docs
TI-2026-53458 Aliases CVE-2026-76403GHSA-xf48-ph6x-76rj

Improper Certificate Validation through HTTP Event Collector Kerberos Authentication in Splunk Connect for Kafka

Priority LOW 34CWE-295Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Spoofing
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-295.

Summary

In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user positioned in the network path could read or alter all relevant data sent from the connector when Kerberos authentication is used with Hypertext Transfer Protocol (HTTP) Event Collector in Splunk Enterprise. The vulnerability is possible because the Kerberos authentication path does not apply the configured certificate validation options when it builds the HTTP client. 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), Security configurations for Splunk Connect for Kafka (https://help.splunk.com/en/splunk-enterprise/get-data-in/splunk-connect-for-kafka/2.2/configure/security-configurations-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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00244 15th percentileScored 2026-11-07
Fix Fixed Splunk Connect for Kafka (Splunk): 2.2.7

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
SplunkSplunk Connect for Kafka2.2 to before 2.2.72.2.7Patch availableCNA
  • Splunk Connect for Kafka VendorSplunk Affected 2.2 to before 2.2.7 Fixed in 2.2.7 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:splunk:connect_for_kafka:*:*:*:*:*:*:*:*before 2.2.7VulnerableSplunk
  • cpe:2.3:a:splunk:connect_for_kafka:*:*:*:*:*:*:*:* Versions before 2.2.7 Vulnerable ·Splunk

Remediation

  • Fix · CNA Splunk Connect for Kafka (Splunk) Fixed in 2.2.7

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Splunk Connect for Kafka 2.2.7

    4 records Highest priority Priority MEDIUM 1 MEDIUM, 3 LOW

    Other records, highest priority first

    • TI-2026-53457 Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for KafkaPriority MEDIUM 42
    • TI-2026-53456 Regular Expression Denial of Service (DoS) through the REST API in Splunk Connect for KafkaPriority LOW 27
    • TI-2026-53455 Denial of Service (DoS) through the REST API in Splunk Connect for KafkaPriority LOW 27
    Show all 4 records →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-76403
  2. 2026-10-03 Alias added: GHSA-xf48-ph6x-76rj

References

Advisory 1

  • TI-2026-53457 Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for Kafka CVSS 3.1HIGH 8.2
  • TI-2026-53456 Regular Expression Denial of Service (DoS) through the REST API in Splunk Connect for Kafka CVSS 3.1MEDIUM 5.9
  • TI-2026-53455 Denial of Service (DoS) through the REST API in Splunk Connect for Kafka CVSS 3.1MEDIUM 5.9

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences