CVE-2026-76317
Last modified
CVE-2026-76317 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who does not hold the "admin" or "power" Splunk roles could move files that the user account running Splunk Enterprise can read into a lookup that the user controls. The user could then access all relevant data and affect system integrity and availability on the search head. EPSS estimates a 0.39% chance of exploitation in the next 30 days.
Description
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who does not hold the "admin" or "power" Splunk roles could move files that the user account running Splunk Enterprise can read into a lookup that the user controls. The user could then access all relevant data and affect system integrity and availability on the search head. The vulnerability is possible because the lookup configuration endpoint does not resolve lookup source paths before checking whether they stay inside the allowed lookup staging area. For more information see About lookups (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/use-lookups-in-splunk-web/about-lookups) and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Splunk | Splunk | >= 9.4.0, < 9.4.14 |
| Splunk | Splunk | >= 10.0.0, < 10.0.9 |
| Splunk | Splunk | >= 10.2.0, < 10.2.6 |
| Splunk | Splunk | >= 10.4.0, < 10.4.2 |
References
- https://advisory.splunk.com/advisories/SVD-2026-0801Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-76317?
How severe is CVE-2026-76317?
How do I fix CVE-2026-76317?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-76311In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …9.4
- CVE-2026-76312In Splunk Enterprise versions below 10.4.1, 10.2.6, 10.0.9, …9.4
- CVE-2026-76313In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8.8
- CVE-2026-76314In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8.8
- CVE-2026-76315In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8.8
- CVE-2026-76316In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.9, …8.8
- CVE-2026-76318In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …5.4
- CVE-2026-76319In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8.8
- CVE-2026-7632A vulnerability was determined in code-projects Online Hospi…7.3
- CVE-2026-76320In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …6.5
- CVE-2026-76321In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …7.3
- CVE-2026-76322In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, …8
Are you affected by CVE-2026-76317?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
