Skip to main content
CVE-2026-131223VulnerabilityPublished

In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could trick an authenticated user into

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131223· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium : upgrade to 8.7.0 when convenient.

Data as of 19 Nov 2026, 22:49 UTC

CVSS 3.1 base score
5.9Medium
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.15.9
Patch
Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:H/PR:N/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

Since the vulnerability requires phishing to trick an authenticated user, organizations should educate users about phishing risks and avoid clicking suspicious links. Monitor official Splunk advisories for patch releases and apply updates to version 8.7.0 or later once available. Until then, limit exposure by restricting access to Splunk Enterprise Security and enforcing strong user authentication policies.

Description

Splunk Enterprise Security versions below 8.7.0 contain a vulnerability where an unauthenticated attacker can craft a malicious link that tricks an authenticated user into executing attacker-controlled Search Processing Language (SPL) commands. This occurs because the Lookup Editor does not properly validate lookup identifiers from URL parameters before including them in searches. Exploitation requires user interaction via phishing, and the attacker cannot exploit the vulnerability without tricking a user. The vulnerability allows access to data and actions permitted to the authenticated user.

References

Community reviews

Loading reviews…