Unauthorized SPL execution via client identifier injection
Published Aug 19, 2026 · Updated Aug 21, 2026
SPL injection in Splunk Enterprise before 10.4.1, 10.2.5, 10.0.9, and 9.4.14 allows remote attackers to run stored searches via the management port. The Deployment Server broker registration flow places attacker-controlled client identifiers into dispatched Add Data forwarder searches without neutralizing special characters, so a crafted identifier becomes part of an SPL pipeline later executed from the workflow. Exploitation requires network reachability to the management port and an administrator to open the Add Data forwarder workflow after the crafted forwarder identity is registered, after which the injected search can read data and affect integrity and availability within the Splunk instance.
Summary
What happened
SPL injection in Splunk Enterprise before 10.4.1, 10.2.5, 10.0.9, and 9.4.14 allows remote attackers to run stored searches via the management port. The Deployment Server broker registration flow places attacker-controlled client identifiers into dispatched Add Data forwarder searches without neutralizing special characters, so a crafted identifier becomes part of an SPL pipeline later executed from the workflow. Exploitation requires network reachability to the management port and an administrator to open the Add Data forwarder workflow after the crafted forwarder identity is registered, after which the injected search can read data and affect integrity and availability within the Splunk instance.
The record
- CVE
- CVE-2026-76316
- Published
- Aug 19, 2026
- Updated
- Aug 21, 2026
- Vendor
- Zoom Video Communications, Inc.
- Product
- Splunk Enterprise
- Classifications
- CWE-943, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 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=10.0 <10.0.9
- Affected versionversion=10.2 <10.2.5
- Affected versionversion=10.4 <10.4.1
- Affected versionversion=9.4 <9.4.14
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