Database compromise via unbound custom-list name
Published Aug 19, 2026 · Updated Aug 21, 2026
SQL injection in Splunk SOAR before 8.6.0 allows remote authenticated users to run arbitrary SQL through playbook custom-list retrieval. The custom-list database lookup incorporates the supplied list name into its query instead of passing it as a bound SQL value. An Automation Engineer role and a playbook are required; successful exploitation permits create, read, update, and delete operations across relevant SOAR database data.
Summary
What happened
SQL injection in Splunk SOAR before 8.6.0 allows remote authenticated users to run arbitrary SQL through playbook custom-list retrieval. The custom-list database lookup incorporates the supplied list name into its query instead of passing it as a bound SQL value. An Automation Engineer role and a playbook are required; successful exploitation permits create, read, update, and delete operations across relevant SOAR database data.
The record
- CVE
- CVE-2026-76365
- Published
- Aug 19, 2026
- Updated
- Aug 21, 2026
- Vendor
- Splunk, Inc.
- Product
- Splunk SOAR
- Classifications
- CWE-74, T1213
- Attack vector
- network
- Privileges
- authenticated
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=8.6 <8.6.0
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