CVE-2026-131238 Code injection in Splunk Enterprise Security

Medium 6.4 Published Updated

A user with run_collect capability can store certificates that run attacker SPL commands when another user views the SSL search dashboard; Splunk Enterprise Security users should care.

Exploited in the wild
Not known
Login needed
Any signed-in user
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-131238?

CVE-2026-131238 is a medium-severity code injection vulnerability in Splunk Enterprise Security, published on 19 Nov 2026. Any signed-in user can exploit it over the network, 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 run_collect capability could store attacker-controlled certificate values. If another user who can access the Secure Sockets Layer Search dashboard selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensitive data and modify data available to the user who selects the row. The vulnerability is possible because the Secure Sockets Layer Search dashboard encodes certificate values for the drilldown link but does not escape the values as SPL search literals before inserting the values into drilldown searches. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Protocol intelligence dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/protocol-intelligence-dashboards) in the Splunk documentation.

Weakness: CWE-943

Which versions are affected by CVE-2026-131238?

An affected version is exposed as installed. No special setting or call is needed.

How do I fix CVE-2026-131238?

No fix has been published for CVE-2026-131238 yet. Limit exposure of the affected software until one is available.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2026-131238 being exploited?

There is no known exploitation of CVE-2026-131238 in the wild and no public exploit code.

Sources

Also known as GHSA-88f2-6wxq-2fmj.

Is CVE-2026-131238 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free