CVE-2026-131216 Stored Cross-Site Scripting (XSS) through Legacy Investigation Workbench Panel Titles in Splunk Enterprise Security
A user with investigation management capability can store script in legacy panel titles that runs in other Splunk users' browsers, exposing Splunk Web data.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Harmful if only installed
- No
- Needs a specific call
- No
- Fix
- None listed
What is CVE-2026-131216?
CVE-2026-131216 is a medium-severity cross-site scripting vulnerability in Splunk Enterprise Security, published on 19 Nov 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official description
In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the manage_all_investigations capability could store attacker-controlled script content in a legacy investigation workbench panel title. Another authenticated user could later open a legacy investigation workbench that renders the panel. The script could then run in the browser of the user who opened the workbench and expose data or actions available through Splunk Web to the user who opened the workbench. The vulnerability is possible because Splunk Enterprise Security does not escape legacy investigation workbench panel titles before rendering them in Splunk Web. For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/capability-reference-for-splunk-enterprise-security) and Review and finish existing legacy investigations in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.4/investigations/review-and-finish-existing-legacy-investigations-in-splunk-enterprise-security) in the Splunk documentation.
Weakness: CWE-79
Which versions are affected by CVE-2026-131216?
An affected version is exposed as installed. No special setting or call is needed.
How do I fix CVE-2026-131216?
No fix has been published for CVE-2026-131216 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-131216 being exploited?
There is no known exploitation of CVE-2026-131216 in the wild and no public exploit code.
Sources
Also known as GHSA-9rpc-x7jj-px64.