Skip to main content

Splunk SOAR CVE-2026-76303

| EUVDEUVD-2026-107648 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-21 cisco GHSA-mr43-r8rx-5q4q
5.7
CVSS 3.1 · Vendor: cisco
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain role with install_apps capability
  2. Delivery
    Install app with malicious documentation content
  3. Exploit
    Phish target user to open app docs
  4. Execution
    Unsanitized script executes in victim browser
  5. Impact
    Act with victim's SOAR permissions

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to already hold a Splunk SOAR role granting the install_apps capability (a trusted administrative permission) and to install an app containing unsanitized, attacker-controlled documentation content. It further requires a second, separate user who holds a role with permission to view apps to be socially engineered (phished) into opening that app's documentation page in their browser - the vendor states the attacker cannot trigger it at will. Limiting factors: both the privileged install_apps capability and mandatory victim user interaction are required, and the product must be running a version below 8.7.0; this is not exploitable against default configurations by unauthenticated or low-privileged users.

Impact

This is a genuine but lower-tier priority: a moderate-severity (CVSS 5.7) stored cross-site scripting (CWE-79) flaw in Splunk SOAR below 8.7.0. The CVSS vector (AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N) is internally consistent with the description - it correctly reflects that the attacker must already hold a privileged role carrying the install_apps capability (PR:H), that successful exploitation requires tricking a second user into viewing the malicious app documentation (UI:R), and that this combination is non-trivial to orchestrate (AC:H). No EPSS score, CISA KEV listing, SSVC decision data, or public POC was provided in the input, so there are no exploitation-probability signals to weigh against the CVSS metrics. Exploitation status is therefore: no public exploit identified at time of analysis. The high privilege requirement (an install_apps role is typically granted only to trusted administrators/engineers) combined with the mandatory social-engineering step substantially limits real-world risk - this is a privilege-escalation/lateral-movement vector within an already-trusted user population rather than an externally reachable unauthenticated bug. Note the vendor explicitly states the attacker 'should not be able to exploit the vulnerability at will' and must phish the victim, which reinforces the AC:H rating. The C:H/I:H impact rating reflects that injected script runs with the victim's session privileges, which could be high if the victim is a SOAR administrator.

Exploit ScenarioDerived

A user holding a role with the install_apps capability installs an app whose documentation embeds malicious, unsanitized HTML/JavaScript. The attacker then phishes a higher-privileged SOAR user into opening that app's documentation page, at which point the script executes in the victim's browser session and performs actions or reads data with the victim's permissions. No public proof-of-concept exploit was identified in the provided intelligence.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Stored cross-site scripting in Splunk SOAR (On-premises) versions below 8.7.0 lets a user holding a role with the install_apps capability embed attacker-controlled HTML/script in an installed app's documentation, which is later rendered unsanitized in the browser of any user who opens that documentation page. Exploitation is not at-will: the vendor requires a second, privileged-but-distinct victim to be phished into viewing the malicious documentation, and the attacker must already possess the trusted install_apps permission, so the CVSS 3.1 score is a moderate 5.7 (AV:N/AC:H/PR:H/UI:R, C:H/I:H/A:N). Successful exploitation lets the attacker act with the victim's privileges - reading data and performing actions the documentation viewer is authorized for; the fix is vendor-released in Splunk SOAR 8.7.0, and no public exploit code was identified at time of analysis.

RemediationAI

Vendor-released patch: upgrade Splunk SOAR (On-premises) to 8.7.0 or later as documented in advisory SVD-2026-1010 (https://advisory.splunk.com/advisories/SVD-2026-1010), and validate any SOAR apps you install after upgrading. Where an immediate upgrade is not possible, reduce exposure by auditing role assignments and removing the install_apps capability from any role that does not strictly require it, so only a minimal set of trusted administrators can install apps (trade-off: this constrains legitimate app deployment workflows and may require a break-glass admin account). Restrict the population of accounts holding app-viewing permissions to users who actually need to browse installed app documentation (trade-off: reduced operational convenience for analysts). Treat installed SOAR apps and their bundled documentation as code from trusted, reviewed sources only, and scan third-party app packages for embedded scripts or unexpected HTML before installation. Educate app-documentation viewers that opening an unfamiliar app's documentation page can trigger script execution in their authenticated session, and advise re-authentication or session termination if a suspicious app was opened - noting that none of these compensating controls removes the underlying unsanitized-rendering flaw, so upgrading to 8.7.0 remains the only complete fix.

Affected VersionsENISA

Splunk SOAR 0 <8.7.0

Affected Packages

euvd splunk_soar fix: 8.7.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This is a stored (persistent) cross-site scripting issue, CWE-79, in the Splunk SOAR web application. Splunk SOAR applications ship with documentation content that the platform renders to users browsing installed apps; the product does not sanitize that documentation before displaying it, so markup injected at install time is preserved and executed in the security context of the Splunk SOAR origin when a different user views the page. Because the injected script runs inside the authenticated SOAR session, it can perform privileged SOAR actions on behalf of the viewing user (consistent with the assessed C:H/I:H/A:N impact) - the classic stored-XSS-to-session-abuse pattern rather than a server-side compromise. The CVSS vector CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N reflects the tight preconditions: the writer must hold the install_apps capability (PR:H), and the reader must be separately tricked into initiating the request in their browser (UI:R, AC:H); scope remains unchanged. Affected per CPE cpe:2.3:a:splunk:splunk_soar:*:*:*:*:*:*:*:* - all on-premises releases prior to 8.7.0.

Know when Splunk gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (cisco) PRIMARY 5.7 MEDIUM
AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
vuln.today AI 5.7 MEDIUM

install_apps capability is a privileged role so PR:H; mandatory phishing/user-initiated request makes it AC:H and UI:R; injected script runs with victim session access giving C:H/I:H, no availability impact.

3.1 AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (cisco).

CVSS VectorVendor: cisco

Attack Vector
Network
Attack Complexity
High
Privileges Required
High
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

1
Patch available
Oct 22, 2026 - 02:16 EUVD

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Medium
enterprise SOAR platform, common in SOCs but not universally deployed
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

More in Splunk

View all
CVE-2014-0160 HIGH POC
7.5 Apr 07

The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe

CVE-2026-20253 CRITICAL POC
9.8 Jun 10

Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.

CVE-2021-22901 HIGH POC
8.1 Jun 11

curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when

CVE-2022-32206 MEDIUM POC
6.5 Jul 07

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple t

CVE-2024-36985 HIGH POC
8.8 Jul 01

In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the admin or powe

CVE-2023-46214 HIGH POC
8.8 Nov 16

In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet la

CVE-2023-32707 HIGH POC
8.8 Jun 01

In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100,

CVE-2022-43571 HIGH POC
8.8 Nov 03

In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through t

CVE-2022-32207 CRITICAL POC
9.8 Jul 07

When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the

CVE-2022-35737 HIGH POC
7.5 Aug 03

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a

CVE-2022-43551 HIGH POC
7.5 Dec 23

A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Rated high seve

CVE-2022-32221 CRITICAL POC
9.8 Dec 05

When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data t

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy