CVE-2026-76365: Structured Query Language (SQL) Injection through Custom Lists in Splunk SOAR

Published Aug 19, 2026
·
Updated

In Splunk SOAR versions below 8.6.0, a user who holds the "Automation Engineer" Splunk SOAR role could run arbitrary Structured Query Language (SQL) statements against the Splunk SOAR database through custom list retrieval in a playbook, allowing for create, read, update, and delete operations on all relevant data stored in the Splunk SOAR database. The SQL injection is possible because Splunk SOAR builds the custom list database lookup with the supplied list name instead of a bound SQL value. For more information see Manage roles and permissions in Splunk SOAR (https://help.splunk.com/en/splunk-soar/soar-cloud/administer-soar-cloud/manage-your-splunk-soar-cloud-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-cloud) and Create custom lists for use in Splunk SOAR playbook comparisons (https://help.splunk.com/en/splunk-soar/soar-cloud/build-playbooks/manage-playbooks-and-playbook-settings/create-custom-lists-for-use-in-splunk-soar-cloud-playbook-comparisons) in the Splunk documentation.

Affected Software

1 affected component
Splunk Splunk SOAR<8.6.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk SOAR to a version that resolves this vulnerability.

    Fixed in 8.6.0

Event History

Aug 19, 2026
CVE Published
via MITRE·09:34 PM
Data Sourced
via MITRE·09:34 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

Exploitation requires a Splunk SOAR user with the Automation Engineer role. The vulnerable path is custom list retrieval performed from a playbook.

2

What level of access could an attacker obtain?

An attacker could execute arbitrary SQL statements against the Splunk SOAR database. This can allow create, read, update, and delete operations on relevant data stored in that database.

3

Which versions are affected?

Splunk SOAR versions below 8.6.0 are affected. Version 8.6.0 is not identified as affected by the provided advisory details.

4

What is the underlying exploitation mechanism?

The custom-list database lookup incorporates the supplied list name rather than using it as a bound SQL value. An Automation Engineer can supply a crafted list name during playbook custom-list retrieval to inject SQL.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203