Skip to main content
CVE-2026-76387VulnerabilityPublished

In Splunk Enterprise Security versions below 8.6.1, a user who holds a Splunk Enterprise Security role that contains

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76387· High 8.1

Not known to be exploited · CVSS 8.1 High : upgrade to 8.6.1 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.6.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 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 17 Nov 2026.

What to do

Upgrade Splunk Enterprise Security to 8.6.1.

Affected software

ProductAffectedFixed in
SplunkSplunk Enterprise SecurityAffected
  • >=8.6 <8.6.1
Fixed in
  • 8.6.1

AI-suggested

Upgrade to Splunk Enterprise Security version 8.6.1 or later, where this vulnerability is addressed. Until patched, restrict roles with the mc_investigation_read capability to trusted users only and avoid using Analyst Queue search filters with untrusted input.

Description

Splunk Enterprise Security versions below 8.6.1 contain a vulnerability where users with roles having the mc_investigation_read capability can inject Search Processing Language (SPL) via Analyst Queue search filters. This occurs because the system does not validate filter field names before including them in SPL searches, potentially allowing unauthorized access to data and system integrity within the scope of scheduled searches for that user.

References

Community reviews

Loading reviews…