Skip to main content
CVE-2026-131216VulnerabilityPublished

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the manage_all_investigations

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131216· Medium 5.7

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

Data as of 19 Nov 2026, 22:49 UTC

CVSS 3.1 base score
5.7Medium
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.7
Patch
Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/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 19 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

AI-suggested

Since the vulnerability affects versions below 8.7.0, upgrading to version 8.7.0 or later is implied as a remediation step. Until patched, restrict roles with the manage_all_investigations capability to trusted users only and avoid opening legacy investigation workbenches containing untrusted panel titles. Monitor Splunk's official advisories for patch releases and remediation guidance.

Description

In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where users with the manage_all_investigations capability can store attacker-controlled script content in legacy investigation workbench panel titles. When another authenticated user opens the affected workbench, the script executes in their browser, potentially exposing data or actions available through Splunk Web. This occurs because legacy panel titles are not properly escaped before rendering.

References

Community reviews

Loading reviews…