CVE-2026-76363: Splunk SOAR SQL injection in REST API

CVE-2026-76363 · Severity: medium · CVSS 6.5 · Published 2026-08-19

Splunk SOAR is a security orchestration platform used to automate incident response workflows. A user with the "Automation Engineer" role can inject SQL commands through the playbook automation REST API, allowing them to read, modify, or delete any data stored in the SOAR database. This undermines data security and could expose sensitive incident response records and customer information.

Technologies: Splunk SOAR. Vendors: Splunk.

Quick answers

Is CVE-2026-76363 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-76363 being exploited in the wild.
How severe is CVE-2026-76363?
Medium severity, with a CVSS score of 6.5, published 19 August 2026.
Which products and versions are affected?
Splunk SOAR below 8.6.0.
Is there a fix for CVE-2026-76363?
A patch was published on 2026-08-19: Fix available in version 8.6.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-76363 attacked?
It is attacked over the network.
Am I affected by CVE-2026-76363?
Check whether you run Splunk SOAR at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a SQL injection (CWE-943) in the Splunk SOAR playbook automation REST API. The API fails to neutralize user-supplied input before incorporating it into database queries. An authenticated user holding the "Automation Engineer" role can craft malicious SQL statements to execute arbitrary queries against the Splunk SOAR database. Successful exploitation allows complete unauthorized access to create, read, update, or delete data. The fix is available in version 8.6.0 and higher.

Affected products

  • Splunk SOAR below 8.6.0

Timeline

  • 2026-08-19: disclosed
  • 2026-08-19: patched: Fix available in version 8.6.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.