Description
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store a malicious ui-tour knowledge object that matches an auto-tour page name and share the object at the app level. The object can execute arbitrary JavaScript in the browser of another authenticated user who visits a standard Splunk Web page. The JavaScript could expose all relevant data and affect system integrity within the second user permissions. The Cross-Site Scripting (XSS) vulnerability is possible because Splunk Web resolves auto-tour entries from the app namespace and uses untrusted tour content when building the tour image.
Published: 2026-08-19
Score: 7.3 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows a user who holds the power role in Splunk Enterprise to craft a malicious ui‑tour knowledge object that matches an auto‑tour page name and share it at the application level. When another authenticated user navigates to a standard Splunk Web page, the untrusted tour content is rendered, enabling the injected JavaScript to run in the victim’s browser. This stored cross‑site scripting can reveal session data, steal credentials, or otherwise compromise the integrity of the victim’s permissions.

Affected Systems

Splunk Enterprise installations running any version older than 10.4.2, 10.2.6, 10.0.9, or 9.4.14 are affected. The flaw requires that Splunk Web be enabled and that an attacker possess the power role to create the malicious tour object; users without that role or when Splunk Web is disabled are not exposed.

Risk and Exploitability

The CVSS score of 7.3 indicates a high severity of the vulnerability. The exploit requires an authenticated attacker who can create a malicious ui‑tour object and a victim who is logged into Splunk Web, so the attack vector is inferred to be authenticated web‑based XSS. EPSS information is unavailable and the issue is not listed in CISA’s KEV catalog. While the impact is limited to users visiting affected pages, the ability to execute code under the victim’s credentials poses a significant threat to data confidentiality and system integrity.

Generated by OpenCVE AI on August 20, 2026 at 09:21 UTC.

Remediation

Vendor Solution

Upgrade Splunk Enterprise to versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14, or higher.


Vendor Workaround

The vulnerability affects instances with Splunk Web turned on. Turning Splunk Web off is a possible workaround. See [Disable unnecessary Splunk Enterprise components](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/install-splunk-enterprise-securely/disable-unnecessary-splunk-enterprise-components) and the [web.conf](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.0-configuration-file-reference/web.conf) configuration specification file for more information on turning off Splunk Web.


OpenCVE Recommended Actions

  • Upgrade Splunk Enterprise to 10.4.2, 10.2.6, 10.0.9, 9.4.14, or newer versions.
  • If an upgrade is not immediately possible, disable Splunk Web by setting http.enable to false in web.conf to stop rendering ui‑tour content.
  • Examine the application namespace for any malicious ui‑tour knowledge objects created by power‑role users and delete them, and limit the power role to trusted personnel.

Generated by OpenCVE AI on August 20, 2026 at 09:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 20 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
First Time appeared Splunk
Splunk splunk Enterprise
Vendors & Products Splunk
Splunk splunk Enterprise

Wed, 19 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
Description In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store a malicious ui-tour knowledge object that matches an auto-tour page name and share the object at the app level. The object can execute arbitrary JavaScript in the browser of another authenticated user who visits a standard Splunk Web page. The JavaScript could expose all relevant data and affect system integrity within the second user permissions. The Cross-Site Scripting (XSS) vulnerability is possible because Splunk Web resolves auto-tour entries from the app namespace and uses untrusted tour content when building the tour image.
Title Stored Cross-Site Scripting (XSS) through Splunk Web in Splunk Enterprise
Weaknesses CWE-79
References
Metrics cvssV3_1

{'score': 7.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N'}


Subscriptions

Splunk Splunk Enterprise
cve-icon MITRE

Status: PUBLISHED

Assigner: cisco

Published:

Updated: 2026-08-19T21:34:29.789Z

Reserved: 2026-08-19T12:02:03.626Z

Link: CVE-2026-76325

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-08-19T22:17:16.650

Modified: 2026-08-20T13:01:19.947

Link: CVE-2026-76325

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-20T09:30:04Z

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')