CVE-2026-76304: Sensitive Information Disclosure through Automation Broker Configuration in Splunk SOAR

Published Oct 21, 2026
·
Updated

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.

Affected Software

1 affected component
Splunk Splunk SOAR<8.7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk SOAR to a version that resolves this vulnerability.

    Fixed in 8.7.0

Event History

Oct 21, 2026
CVE Published
via MITRE·10:52 PM
Data Sourced
via MITRE·10:52 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Which users can exploit this issue?

Any authenticated Splunk SOAR user on an affected version can exploit it if they lack Automation Broker edit permission. The missing permission check allows those lower-privileged users to download the Automation Broker Docker Compose configuration file.

2

What information can be exposed?

The downloadable configuration file contains the Splunk SOAR instance URL, the container image location, and the Splunk SOAR Automation Broker version. The provided data does not indicate exposure of credentials or other secrets.

3

Are installations running Splunk SOAR 8.7.0 or later affected?

No. The issue is described as affecting Splunk SOAR versions below 8.7.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203