Skip to main content
VulnerabilityPublished

CVE-2026-131227: 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 6.3 Medium : upgrade to 8.7.0 when convenient.

Data as of 19 Nov 2026, 20:39 UTC

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

Upgrade Splunk Enterprise Security to version 8.7.0 or later, where this vulnerability is fixed. No other mitigation or workaround is documented. Users should ensure that roles with the run_collect capability are assigned carefully to trusted users only.

Description

CVE-2026-131227 affects Splunk Enterprise Security versions prior to 8.7.0. It allows a user with the run_collect capability to store attacker-controlled values in Network Resolution data, which can lead to another user executing attacker-controlled SPL commands via the Domain Name System Search dashboard. This occurs because the dashboard does not properly escape data-model field values before inserting them into drilldown searches. The vulnerability is fixed in version 8.7.0.

References

Community reviews

Loading reviews…