CVE-2026-76402Network attack vector

Credential exposure via insecure HEC endpoint

Published Aug 19, 2026 · Updated Aug 20, 2026

Server-side request forgery in Splunk Connect for Kafka before 2.2.7 allows remote attackers to expose HEC credentials via the REST API. The Kafka Connect management API accepts attacker-supplied splunk.hec.uri values, and affected versions did not require HTTPS by default, so the connector could post its HEC token and event traffic to an attacker-controlled HTTP endpoint. Exposure requires network reachability to an unauthenticated Kafka Connect REST API; theft of the HEC token can expose all data sent through the connector and let the attacker influence event delivery for that connector.

CVSS severity8.2
High
EPSS probability0.30%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Server-side request forgery in Splunk Connect for Kafka before 2.2.7 allows remote attackers to expose HEC credentials via the REST API. The Kafka Connect management API accepts attacker-supplied splunk.hec.uri values, and affected versions did not require HTTPS by default, so the connector could post its HEC token and event traffic to an attacker-controlled HTTP endpoint. Exposure requires network reachability to an unauthenticated Kafka Connect REST API; theft of the HEC token can expose all data sent through the connector and let the attacker influence event delivery for that connector.

The record

CVE
CVE-2026-76402
Published
Aug 19, 2026
Updated
Aug 20, 2026
Vendor
Zoom Video Communications, Inc.
Product
Splunk Connect for Kafka
Classifications
CWE-918, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.2 <2.2.7

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Zoom Video Communications, Inc. · Splunk Connect for Kafkaversion=2.2 <2.2.7

Published CVSS scores

8.2SplunkCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo