EUVD-2026-36089
GHSA-xg25-vr2h-r356
Severity by source
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.11, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the "admin" or "power" Splunk roles could store a malicious script in a classic dashboard HTML panel, causing unauthorized JavaScript code to execute in the browser of another user.
The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The low-privileged user should not be able to exploit the vulnerability at will.
AnalysisAI
Stored cross-site scripting in Splunk Enterprise (below 10.2.4, 10.0.7, 9.4.12, 9.3.13) and Splunk Cloud Platform (below 10.3.2512.11, 10.2.2510.15, 10.1.2507.23, 9.3.2411.132) allows a low-privileged authenticated user - without 'admin' or 'power' roles - to embed malicious JavaScript inside a classic dashboard HTML panel that executes in another user's browser session. Exploitation requires phishing the victim into initiating a specific browser request, and no public exploit was identified at time of analysis.
Technical ContextAI
The flaw is a CWE-79 (Improper Neutralization of Input During Web Page Generation) issue in the legacy 'classic' dashboard framework of Splunk's web UI, specifically the HTML panel component which historically permitted raw HTML/JavaScript markup for dashboard customization. The CPE data identifies both the self-managed product (cpe:2.3:a:splunk:splunk_enterprise) and the SaaS offering (cpe:2.3:a:splunk:splunk_cloud_platform), indicating the vulnerable HTML panel rendering path is shared across both deployment models. Because Splunk dashboards are typically authenticated viewing surfaces tied to high-privilege analyst, SOC, and admin workflows, stored XSS inside a panel becomes a privilege-escalation primitive rather than a generic web XSS.
RemediationAI
Vendor-released patches are available: upgrade Splunk Enterprise to 10.2.4, 10.0.7, 9.4.12, or 9.3.13 (matching your current maintenance branch), per the advisory at https://advisory.splunk.com/advisories/SVD-2026-0608; Splunk Cloud Platform customers should confirm they have been rolled forward to 10.3.2512.11, 10.2.2510.15, 10.1.2507.23, or 9.3.2411.132 since that is vendor-operated. Until patched, restrict who can create or edit classic dashboards by reviewing role capabilities (notably 'edit_view_html' and the ability to author HTML panels) and removing those capabilities from low-privileged users, and migrate critical dashboards to the modern Dashboard Studio framework which does not expose the HTML panel - the trade-off is loss of legacy custom-HTML functionality and an audit/conversion effort. Additionally, enforce phishing-resistant browser hygiene for analysts (warn users not to click dashboard links from untrusted sources) since the bug requires victim-initiated request flow.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.
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
In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet la
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,
In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through t
When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data t
When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the
A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functional
When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer
A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly re
A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an atta
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today