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.
CVE-2026-76317
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-20. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 21, 2026
Advisory Details (1)
Auto-updated Aug 19, 2026SVD-2026-0801 | Splunk Vulnerability Disclosure
https://advisory.splunk.com/advisories/SVD-2026-0801Vendor Advisories for CVE-2026-76317(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 04:35 UTCEG score recompute
- 2026-08-21 04:35 UTCGHSA enrichment
- 2026-08-21 04:00 UTCEG score recompute
- 2026-08-21 04:00 UTCGHSA enrichment
- 2026-08-21 01:59 UTCEG score recompute
- 2026-08-21 01:59 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 13:44 UTCGHSA enrichment
- 2026-08-20 13:24 UTCGHSA enrichment
- 2026-08-20 10:37 UTCEG score recompute
- 2026-08-20 10:37 UTCGHSA enrichment
- 2026-08-19 22:22 UTCEG score recompute
- 2026-08-19 21:40 UTCEG score recompute
- 2026-08-19 21:37 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-76317?
When was CVE-2026-76317 disclosed?
Is CVE-2026-76317 actively exploited?
What is the CVSS score of CVE-2026-76317?
How do I remediate CVE-2026-76317?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76317
Is Your Infrastructure Affected by CVE-2026-76317?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.