In Splunk SOAR versions below 8.7.0, an authenticated user who does not hold a role with permission to edit Automation Brokers could download the Splunk SOAR Automation Broker Docker Compose configuration file. The file contains the Uniform Resource Locator (URL) of the Splunk SOAR instance, the container image location, and the Splunk SOAR Automation Broker version. The vulnerability is possible because Splunk SOAR returns the configuration file without enforcing the Automation Broker edit permission. For more information see Install Splunk Automation Broker on a Docker host (https://help.splunk.com/en/splunk-soar/splunk-automation-broker/install-and-create-classic-splunk-soar-automation-brokers/install-splunk-automation-broker-on-a-docker-host) and Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.5.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) 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 4.3 · splunkNVD modified 2026-10-21 22:52
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.