Skip to content
Applications

CVE-2026-76402

8.2
High
EPSS 0.30%Patch availableAug 21, 2026

Unauthenticated attacker can make Splunk Kafka connector leak HEC credentials via HTTP.

common questions

Is CVE-2026-76402 being exploited?

Not confirmed. CVE-2026-76402 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-76402?

CVE-2026-76402 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-76402?

Yes. A fix has been recorded for CVE-2026-76402. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-76402 affect?

CVE-2026-76402 affects Splunk Connect for Kafka < 2.2.7, Splunk Enterprise HTTP Event Collector (HEC) endpoints (if configured over HTTP), Kafka Connect REST API. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76402?

Upgrade to Splunk Connect for Kafka 2.2.7+, enforce HTTPS for HEC, restrict REST API access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Splunk Connect for Kafka < 2.2.7Splunk Enterprise HTTP Event Collector (HEC) endpoints (if configured over HTTP)Kafka Connect REST API
impact

Unauthenticated actor with access to Kafka Connect REST can configure non-secure HTTP HEC, exfiltrate Splunk credentials and potentially alter/interrupt ingested events.

action required

Immediate action required

affected versions
Splunk Splunk Connect for Kafka
  • affected>= 2.2 and < 2.2.7

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free