Skip to main content
VulnerabilityPublished Updated

CVE-2026-76387: Splunk Enterprise Security · The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program.

Affects Splunk Enterprise SecuritySource CVE Database V5

0
Compare

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

Data as of 16 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 16 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 Splunk Enterprise Security to version 8.6.1 or later, where this vulnerability is fixed. Since the vulnerability is due to improper input validation, applying the official patch eliminates the risk. No other mitigations are indicated by the vendor advisory. Patch status is confirmed by the version range affected and fixed version 8.6.1.

Description

CVE-2026-76387 is a high-severity vulnerability in Splunk Enterprise Security versions 8.6 up to but not including 8.6.1. It allows users with the mc_investigation_read capability to inject Search Processing Language (SPL) commands via Analyst Queue search filters due to improper validation of filter field names. This can lead to unauthorized access to data and system integrity as permitted by the scheduled searches run for that user.

References

Community reviews

Loading reviews…