Skip to main content
VulnerabilityPublished

CVE-2026-131208: Splunk Enterprise Security · The software constructs all or part of a command, data structure, or record using

Affects Splunk Enterprise SecuritySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 8.7.0 when convenient.

Data as of 19 Nov 2026, 20:04 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (cisco)CVSS 3.15.9
Patch
Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Splunk Enterprise Security to 8.7.0.

Affected software

ProductAffectedFixed in
SplunkSplunk Enterprise SecurityAffected
  • <8.7.0
Fixed in
  • 8.7.0

Description

In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could create and deliver a crafted Investigation Workbench link to an authenticated Splunk Enterprise Security user. If the authenticated user opens the link, Investigation Workbench could run arbitrary Search Processing Language (SPL) commands using the permissions of the authenticated user. With this access, the unauthenticated user could expose or modify data available to the authenticated user. The vulnerability is possible because Investigation Workbench does not safely neutralize special characters in artifact values before adding the values to searches. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Investigate a potential security incident on the investigation workbench in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-7/user-guide/7.3/investigations/investigate-a-potential-security-incident-on-the-investigation-workbench-in-splunk-enterprise-security) and Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) in the Splunk documentation.

References

Community reviews

Loading reviews…