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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 6
- StatusUndergoing Analysis → PublishedNVD modified 2026-10-26 16:46
- StatusAwaiting Analysis → Undergoing AnalysisNVD modified 2026-10-26 17:17
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-22 16:57
- StatusReceived → PublishedNVD modified 2026-10-21 22:52
- StatusPublished → ReceivedNVD modified 2026-10-21 23:17
- First seenCVSS 6.5 · splunkNVD modified 2026-10-21 22:52
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.