CVE-2026-76387
SPL injection via Analyst Queue in Splunk ES (<8.6.1) enables unauthorized data access
Is CVE-2026-76387 being exploited?
Not confirmed. CVE-2026-76387 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-76387?
CVE-2026-76387 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-76387?
Yes. A fix has been recorded for CVE-2026-76387. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76387 affect?
CVE-2026-76387 affects Splunk Enterprise Security < 8.6.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76387?
Upgrade to Splunk ES 8.6.1; restrict mc_investigation_read, audit and rotate privileged accounts
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated mc_investigation_read users can inject SPL in search filters to read/alter data and leverage scheduled searches' privileges.
Immediate action required
- affected>= 8.6 and < 8.6.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.