CVE-2026-76403: Improper Certificate Validation through HTTP Event Collector Kerberos Authentication in Splunk Connect for Kafka

Published Aug 19, 2026
·
Updated

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.

Affected Software

1 affected component
Splunk Splunk Connect for Kafka<2.2.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk Connect for Kafka to a version that resolves this vulnerability.

    Fixed in 2.2.7

Event History

Aug 19, 2026
CVE Published
via MITRE·09:35 PM
Data Sourced
via MITRE·09:35 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Splunk Connect for Kafka versions below 2.2.7 are exposed when they use Kerberos authentication with Splunk Enterprise HTTP Event Collector. The issue affects the HTTP client created through that Kerberos authentication path.

2

What does an attacker need to exploit it?

An attacker must be positioned on the network path between the connector and the relevant HTTP Event Collector communication. No authentication or user interaction is required.

3

What could an attacker do if exploitation succeeds?

A network-path attacker could read or alter all relevant data sent from the connector. Availability is not identified as affected.

4

Does configuring certificate validation protect the affected Kerberos path?

No. The affected Kerberos authentication path does not apply the configured certificate validation options when building its HTTP client.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203