High [CVE-2026-76387] SPL Injection through the REST API in Splunk Enterprise Security
This high-severity Splunk advisory covers CVE-2026-76387 affecting Splunk Enterprise Security.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published
Android app · Google Play
Monitor future Splunk CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
In Splunk Enterprise Security versions below 8.6.1, a user who holds a Splunk Enterprise Security role that contains the mc_investigation_read capability could inject Search Processing Language (SPL) through Analyst Queue search filters, allowing for access to all relevant data and system integrity available to the scheduled searches that run for that user.
The vulnerability is possible because the Analyst Queue search filter handling does not validate filter field names before the fields are included in SPL searches.
For more information see Users and roles for Splunk Enterprise Security ( ), Manage analyst workflows using the analyst queue in Splunk Enterprise Security ( ), and Overview of Mission Control in Splunk Enterprise Security ( ) in the Splunk documentation.
- Splunk Enterprise Security 8.6 before 8.6.1
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Mitigation
Upgrade to a fixed release: 8.6.1. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.