Skip to main content
CVE-2026-131229VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131229· Medium 5.4

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

Data as of 19 Nov 2026, 22:40 UTC

CVSS 3.1 base score
5.4Medium
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.4
Patch
Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/PR:L/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 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

Users should upgrade to Splunk Enterprise Security version 8.7.0 or later once available, as the vulnerability affects versions below 8.7.0. Until then, restrict the run_collect capability to trusted roles only and limit access to the Vulnerability Search dashboard to minimize risk.

Description

In Splunk Enterprise Security versions below 8.7.0, a vulnerability exists where a user with the run_collect capability can inject attacker-controlled values into vulnerability data. When another user accesses the Vulnerability Search dashboard and selects an affected row, the system may execute attacker-controlled Search Processing Language (SPL) commands with the permissions of the selecting user. This occurs because the dashboard encodes data-model field values for drilldown links but fails to escape them properly as SPL search literals. This flaw could allow unauthorized access to sensitive data and modification of some data accessible to the selecting user.

References

Community reviews

Loading reviews…