Splunk Enterprise is widely used across organizations; this flaw allows non-admins to expose data and disrupt SIEM/search heads, risking broad operational impact.
CVE-2026-76317
Non-admin can move readable files into user-controlled lookups, exposing data and disrupting search heads.
Is CVE-2026-76317 being exploited?
Not confirmed. CVE-2026-76317 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.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-76317?
CVE-2026-76317 is rated High with a CVSS score of 8.8. 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-76317?
Yes. A fix has been recorded for CVE-2026-76317. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76317 affect?
CVE-2026-76317 affects Splunk Enterprise < 10.4.2, Splunk Enterprise < 10.2.6, Splunk Enterprise < 10.0.9, Splunk Enterprise < 9.4.14, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76317?
Upgrade to the fixed Splunk versions, restrict lookup permissions and audit file access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Non-admin users can move readable files into lookups they control to access sensitive data, undermine search-head integrity, and affect availability.
Immediate action required
- affected>= 10.4 and < 10.4.2
- affected>= 10.2 and < 10.2.6
- affected>= 10.0 and < 10.0.9
- affected>= 9.4 and < 9.4.14
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.