Service interruption via unbounded timestamp regex
Published Aug 19, 2026 · Updated Aug 20, 2026
Denial of service in timestamp extraction in Splunk Connect for Kafka before 2.2.7 allows remote attackers to stop event delivery via the REST API. The connector accepts attacker-configured timestamp.regex patterns through the Kafka Connect REST API and evaluates them against event data without a time limit, letting a crafted pattern and matching payload block a Kafka Connect worker thread; the 2.2.7 release notes state that a timeout was added to timestamp matching. Reachability requires unauthenticated access to the administrative Kafka Connect REST API and control over matching event content, and the documented consequence is interruption of the affected connector's delivery path rather than broader host compromise.
Summary
What happened
Denial of service in timestamp extraction in Splunk Connect for Kafka before 2.2.7 allows remote attackers to stop event delivery via the REST API. The connector accepts attacker-configured timestamp.regex patterns through the Kafka Connect REST API and evaluates them against event data without a time limit, letting a crafted pattern and matching payload block a Kafka Connect worker thread; the 2.2.7 release notes state that a timeout was added to timestamp matching. Reachability requires unauthenticated access to the administrative Kafka Connect REST API and control over matching event content, and the documented consequence is interruption of the affected connector's delivery path rather than broader host compromise.
The record
- CVE
- CVE-2026-76401
- Published
- Aug 19, 2026
- Updated
- Aug 20, 2026
- Vendor
- Zoom Video Communications, Inc.
- Product
- Splunk Connect for Kafka
- Classifications
- CWE-407, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=2.2 <2.2.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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