In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a low-privileged user that does not hold the fsh_manage capability could perform Remote Code Execution through Federated Search bundle selection. This could allow for access to all relevant data and affect system integrity and availability. The vulnerability is possible because the Federated Search dispatch flow accepts caller-controlled bundle selection without enforcing the capability that manages federated providers and indexes. For more information see Security models for Federated Search for Splunk (https://help.splunk.com/en/splunk-enterprise/search/federated-search/10.4/run-federated-searches-across-other-splunk-deployments/service-accounts-and-security-for-federated-search-for-splunk/security-models-for-federated-search-for-splunk) 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-76319
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
- 44(Track)EG Risk 44/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%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 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-76319(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 7× in last 7d / 7× 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-20 13:43 UTCGHSA enrichment
- 2026-08-20 13:23 UTCGHSA enrichment
- 2026-08-20 09:29 UTCEG score recompute
- 2026-08-20 09:29 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(4)
What is CVE-2026-76319?
When was CVE-2026-76319 disclosed?
What is the CVSS score of CVE-2026-76319?
How do I remediate CVE-2026-76319?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76319
Is Your Infrastructure Affected by CVE-2026-76319?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.