Skip to main content
CVE-2026-131239VulnerabilityPublished

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-131239· High 7.3

Not known to be exploited · CVSS 7.3 High : upgrade to 8.7.0 soon.

Data as of 19 Nov 2026, 22:39 UTC

CVSS 3.1 base score
7.3High
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.17.3
Patch
Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:L/PR:L/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 then, restrict the run_collect capability to trusted users only and limit access to the System Update Status report to minimize exposure.

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 Updates data. When another user with access to the System Update Status report selects an affected row, Splunk may execute attacker-controlled Search Processing Language (SPL) commands with the selecting user's permissions. This occurs because the report does not validate certain input fields before using them in drilldown searches, potentially allowing unauthorized data access and modification.

References

Community reviews

Loading reviews…