---
id: "CVE-2026-76304"
kind: "vulnerability"
aliases: ["CVE-2026-76304"]
title: "Splunk SOAR: low-privilege users can download Automation Broker Docker config"
severity: "medium"
cvss: 4.3
epss: 0.00162
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "self-hosted", "splunk-soar"]
not_affected_if: ["no-untrusted-users", "version-8.7.0-or-later"]
published_at: "2026-10-21T23:17:28+00:00"
first_seen_at: "2026-10-23T21:57:29+00:00"
updated_at: "2026-10-25T04:37:33+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-76304", "first_seen_at": "2026-10-23T21:57:29+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-76304", "first_seen_at": "2026-10-24T13:15:54+00:00"}]
---

# Splunk SOAR: low-privilege users can download Automation Broker Docker config

Splunk SOAR versions below 8.7.0 return the Automation Broker Docker Compose file to authenticated users who lack permission to edit brokers. That file exposes the SOAR instance URL, the container image location and the broker version.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Splunk SOAR version on the instance; `unknown` for the exact command, the sources do not say.
- Review which roles hold Automation Broker edit permission in Splunk SOAR (On-premises) role settings.

## Fix

- Upgrade Splunk SOAR to `8.7.0` or later.

## Timeline

- 2026-10-23T21:57:29+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-76304
- 2026-10-24T13:15:54+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-76304

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_