Skip to main content
CVE-2026-131224VulnerabilityPublished

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-131224· Low 3.7

Not known to be exploited · CVSS 3.7 Low : upgrade to 8.7.0 when convenient.

Data as of 19 Nov 2026, 22:49 UTC

CVSS 3.1 base score
3.7Low
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.13.7
Patch
Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/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 App for PCI Compliance to 8.7.0.

Affected software

ProductAffectedFixed in
SplunkSplunk App for PCI ComplianceAffected
  • <8.7.0
Fixed in
  • 8.7.0

AI-suggested

If you cannot patch yet, restrict roles with the run_collect capability to trusted users only and limit pci_analyst role users from interacting with untrusted report data. Review and apply any vendor guidance once published.

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 the Endpoint Changes report. Another user with the pci_analyst role could trigger the execution of attacker-controlled Search Processing Language (SPL) commands by interacting with the report. This occurs because the report does not properly treat dynamic values as literal search inputs, allowing command injection with the permissions of the clicking user.

References

Community reviews

Loading reviews…