Structured Query Language Injection through the REST API in Splunk SOAR

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Splunk/Splunk SOAR (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Splunk/Splunk SOAR.
2. 2Review the reported fix. Update Splunk/Splunk SOAR to 8.6.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Aug 19, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 19, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 19, 2026

Sources and claim methodology

• Source referenceadvisory.splunk.com

Related CVEs

• Server-Side Request Forgery (SSRF) through the Connectivity Check REST API in Splunk SOARSame splunk/splunk soar package
• Improper Certificate Validation through CyberArk Vault Privileged Access Manager in Splunk SOARSame splunk/splunk soar package
• Structured Query Language (SQL) Injection through Custom Function Results in Splunk SOARSame splunk/splunk soar package
• Structured Query Language (SQL) Injection through Custom Lists in Splunk SOARSame splunk/splunk soar package
• Information Disclosure through the REST API in Splunk SOARSame splunk/splunk soar package
• Stored Cross-Site Scripting (XSS) through Notes in Splunk SOARSame splunk/splunk soar package