PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-76400 Splunk CVE debrief

An AI-assisted PatchSiren debrief based on the supplied source corpus. CVE-2026-76400 affects Splunk Connect for Kafka versions below 2.2.7, allowing an unauthenticated user who can reach the Kafka Connect REST API and influence responses from an HTTP Event Collector endpoint to cause the connector to retry failed event batches until event delivery stops. This occurs because HTTP Event Collector delivery retry handling uses an unbounded default for failed batches instead of a finite retry limit. Organizations using Splunk Connect for Kafka versions below 2.2.7 should prioritize updating to a fixed version. The vulnerability is possible due to the unbounded default retry handling for failed batches in HTTP Event Collector delivery. Security teams and administrators responsible for data ingestion and monitoring should be aware of the potential for denial-of-service conditions and take proactive measures to mitigate the risk. Evidence from the CVE Program and NVD indicates that unauthenticated users could cause the connector to retry failed event batches, potentially stopping event delivery. The CVE record was published on 2026-08-19T22:17:26.647Z and has not been modified since then.

Vendor
Splunk
Product
Splunk Connect for Kafka
CVSS
MEDIUM 5.9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-19
Original CVE updated
2026-08-24
Advisory published
2026-08-19
Advisory updated
2026-08-24

Who should care

Organizations using Splunk Connect for Kafka versions below 2.2.7 should prioritize updating to a fixed version. Security teams and administrators responsible for data ingestion and monitoring should be aware of the potential for denial-of-service conditions and take proactive measures to mitigate the risk.

Technical summary

CVE-2026-76400 affects Splunk Connect for Kafka versions below 2.2.7. An unauthenticated user who can reach the Kafka Connect REST API and influence responses from an HTTP Event Collector endpoint could cause the connector to retry failed event batches until event delivery stops. This occurs because HTTP Event Collector delivery retry handling uses an unbounded default for failed batches instead of a finite retry limit.

Defensive priority

Medium-priority defensive actions are recommended due to the potential for denial of service through event delivery disruption in Splunk Connect for Kafka versions below 2.2.7.

Recommended defensive actions

  • Review and update Splunk Connect for Kafka to version 2.2.7 or later.
  • Implement compensating controls to monitor and limit excessive retry attempts.
  • Verify and adjust HTTP Event Collector configurations to prevent unbounded retries.
  • Monitor for and respond to potential denial-of-service conditions.
  • Consult vendor advisory SVD-2026-0808 for additional guidance.

Evidence notes

Evidence from the CVE Program and NVD indicates that unauthenticated users could cause the connector to retry failed event batches, potentially stopping event delivery. The issue arises from unbounded default retry handling for failed batches in HTTP Event Collector delivery. Vendor advisory SVD-2026-0808 provides additional context.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-76400 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-76400

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-76400 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-76400

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.