---
id: "CVE-2026-76303"
kind: "vulnerability"
aliases: ["CVE-2026-76303"]
title: "Splunk SOAR: app documentation runs attacker script in other users' browsers"
severity: "medium"
cvss: 5.7
epss: 0.00176
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["other", "security-operations", "self-hosted", "splunk-soar"]
not_affected_if: ["no-install_apps-users", "splunk-soar-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:10:26+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-76303", "first_seen_at": "2026-10-23T21:57:29+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-76303", "first_seen_at": "2026-10-24T13:15:54+00:00"}]
---

# Splunk SOAR: app documentation runs attacker script in other users' browsers

Splunk SOAR below 8.7.0 does not sanitize app documentation, so a user with the install_apps capability can store script that runs in the browser of another user who opens that documentation. The attacker can then act with the victim's access to data and changes, but only if the victim is tricked into a crafted browser request.

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

## How to check

- Check the installed Splunk SOAR version in the product's about page or with `unknown` on the command line; the sources do not name a command.
- Review which accounts hold a role with the install_apps capability in Splunk SOAR role settings.

## Fix

- Upgrade Splunk SOAR on-premises to `8.7.0` or later.

## Timeline

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

## From the sources

In Splunk SOAR versions below 8.7.0, a user that holds a role with the install_apps capability could store attacker-controlled content that Splunk SOAR displays in app documentation by installing an app. If another user who holds a role with permission to view apps opens the app documentation, Splunk SOAR could run that content in the browser of the user who opened the app documentation. With this access, the first user could access data and make changes that the user who opened the app documentation could make.
The vulnerability is possible because Splunk SOAR does not sanitize app documentation content before it displays that content.
The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The user that holds a role with the install_apps capability should not be able to exploit the vulnerability at will.
For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/7.1.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) and Add and configure apps and assets to provide actions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.6.0/manage-your-splunk-soar-on-premises-apps-and-assets/add-and-configure-apps-and-assets-to-provide-actions-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_