Skip to main content
VulnerabilityPublished

CVE-2026-131211: Splunk Enterprise Security · The application generates a query intended to access or manipulate data

Affects Splunk Enterprise SecuritySource CVE Database V5

0
Compare

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

Data as of 19 Nov 2026, 20:37 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

Upgrade to Splunk App for Payment Card Industry Compliance version 8.7.0 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated by the vendor advisory.

Description

CVE-2026-131211 is a vulnerability in Splunk App for Payment Card Industry Compliance versions prior to 8.7.0. It allows a user with the "ess_user" role to inject attacker-controlled values into lookup data used by the Primary Functions report. When another authenticated user selects these values, the app may execute attacker-controlled SPL commands with the permissions of the selecting user. This occurs because the report does not properly escape values before including them in drilldown searches. The issue is fixed in version 8.7.0.

References

Community reviews

Loading reviews…