CVE-2026-76308: Missing Authorization through the REST API in Splunk SOAR
In Splunk SOAR versions below 8.7.0, an authenticated user could change the Enterprise Security edition through the Representational State Transfer (REST) API and cause Splunk SOAR to apply the license change. The vulnerability is possible because Splunk SOAR authenticates requests to manage the Enterprise Security edition but does not authorize the caller before it applies the license change. For more information see Using the REST API reference for Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/8.7.0/using-the-splunk-soar-rest-api/using-the-rest-api-reference-for-splunk-soar-on-premises), Obtain and configure a Splunk SOAR (On-premises) license (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.7.0/configure-your-companys-settings-in-splunk-soar-on-premises/obtain-and-configure-a-splunk-soar-on-premises-license), and Integration of Splunk SOAR with Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/automation-with-playbooks/integration-of-splunk-soar-with-splunk-enterprise-security) in the Splunk documentation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk SOARto a version that resolves this vulnerability.Fixed in 8.7.0
Event History
Frequently Asked Questions
Which deployments are affected?
Splunk SOAR versions below 8.7.0 are affected. The issue concerns management of the Enterprise Security edition through the REST API.
What does an attacker need to exploit this issue?
An attacker needs to be authenticated to Splunk SOAR. No additional authorization to manage the Enterprise Security edition is required before the license change is applied.
What could an attacker do?
An authenticated user could change the Enterprise Security edition through the REST API, causing Splunk SOAR to apply the license change.
What version addresses the issue?
Version 8.7.0 is not included in the affected version range described in the advisory.