Skip to main content
CVE-2026-131214VulnerabilityPublished

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the edit_timeline capability could

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131214· Medium 4.8

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

Data as of 19 Nov 2026, 22:49 UTC

CVSS 3.1 base score
4.8Medium
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.14.8
Patch
Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/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 recommended if such a version includes a fix. Until a fix is confirmed, restrict roles with edit_timeline and manage_all_investigations capabilities to trusted users only. Monitor Splunk's official advisories for patch availability and apply updates promptly once released.

Description

In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the edit_timeline capability can store attacker-controlled Search Processing Language (SPL) in a legacy investigation timeline entry. Another user with the manage_all_investigations capability could later execute this stored SPL with their own permissions, potentially accessing data they are authorized to see. This occurs because stored investigation search content is not treated as a literal search before execution. The vulnerability has a CVSS score of 4.8 (medium severity).

References

Community reviews

Loading reviews…