Skip to main content
CVE-2026-131211VulnerabilityPublished

In Splunk App for Payment Card Industry Compliance versions below 8.7.0, a user who holds the "ess_user" Splunk

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131211· 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:48 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. Users should review Splunk's official documentation and advisories for the Splunk App for PCI Compliance and Enterprise Security roles to apply the appropriate fixes or mitigations. Until patched, restrict the "ess_user" role permissions or limit access to the Primary Functions report to trusted users only.

Description

A vulnerability in Splunk App for Payment Card Industry Compliance versions below 8.7.0 allows users with the "ess_user" role to inject attacker-controlled values into lookup data used by the Primary Functions report. This can lead to execution of attacker-controlled SPL commands with the permissions of another authenticated user who interacts with the manipulated report. The issue arises because the report does not properly escape values before including them in drilldown searches.

References

Community reviews

Loading reviews…