In Splunk Enterprise Security versions below 8.6.1, a user who holds a Splunk Enterprise Security role that contains the mc_investigation_read… (CVE-2026-76387)
Splunk Enterprise Security versions below 8.6.1 contain a vulnerability where users with roles including the mc_investigation_read capability can inject Search Processing Language (SPL) via Analyst Queue search filters. This occurs because the filter field names are not validated before inclusion in SPL searches. The vulnerability allows access to all data and system integrity accessible to the scheduled searches run by that user.
AI Analysis
Technical Summary
In Splunk Enterprise Security versions prior to 8.6.1, a vulnerability exists due to improper validation of filter field names in Analyst Queue search filters. Users with a role containing the mc_investigation_read capability can inject arbitrary SPL commands, potentially accessing all data and system integrity available to their scheduled searches. This is classified under CWE-20 (Improper Input Validation) and has a CVSS 3.1 score of 8.1, indicating high severity. No known exploits in the wild have been reported. The vulnerability is fixed in version 8.6.1.
Potential Impact
An attacker with a Splunk Enterprise Security role that includes mc_investigation_read can perform SPL injection via Analyst Queue search filters, leading to unauthorized access to all relevant data and system integrity within the scope of the scheduled searches run by that user. This can result in high confidentiality and integrity impact without affecting availability.
Mitigation Recommendations
Upgrade Splunk Enterprise Security to version 8.6.1 or later, where this vulnerability is fixed. Since this is not a cloud service, remediation requires applying the official patch. Until patched, restrict roles with mc_investigation_read capability to trusted users only.
In Splunk Enterprise Security versions below 8.6.1, a user who holds a Splunk Enterprise Security role that contains the mc_investigation_read… (CVE-2026-76387)
Description
Splunk Enterprise Security versions below 8.6.1 contain a vulnerability where users with roles including the mc_investigation_read capability can inject Search Processing Language (SPL) via Analyst Queue search filters. This occurs because the filter field names are not validated before inclusion in SPL searches. The vulnerability allows access to all data and system integrity accessible to the scheduled searches run by that user.
CVSS v3.1
Score 8.1high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Splunk Enterprise Security versions prior to 8.6.1, a vulnerability exists due to improper validation of filter field names in Analyst Queue search filters. Users with a role containing the mc_investigation_read capability can inject arbitrary SPL commands, potentially accessing all data and system integrity available to their scheduled searches. This is classified under CWE-20 (Improper Input Validation) and has a CVSS 3.1 score of 8.1, indicating high severity. No known exploits in the wild have been reported. The vulnerability is fixed in version 8.6.1.
Potential Impact
An attacker with a Splunk Enterprise Security role that includes mc_investigation_read can perform SPL injection via Analyst Queue search filters, leading to unauthorized access to all relevant data and system integrity within the scope of the scheduled searches run by that user. This can result in high confidentiality and integrity impact without affecting availability.
Mitigation Recommendations
Upgrade Splunk Enterprise Security to version 8.6.1 or later, where this vulnerability is fixed. Since this is not a cloud service, remediation requires applying the official patch. Until patched, restrict roles with mc_investigation_read capability to trusted users only.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-p274-gc4j-gjpj
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-76387"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a870a83acd9273b49b59830
Added to database: 08/20/2026, 14:09:07 UTC
Last enriched: 08/20/2026, 14:41:57 UTC
Last updated: 08/20/2026, 21:51:58 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.