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 inject arbitrary Search Processing Language (SPL) commands through the geostats command. The injected SPL runs with the permissions of another authenticated user after that user initiates the attacker-controlled geostats search in Splunk Web. The injected SPL could expose all relevant data available to the second user, including stored credentials, and modify lookup files that the second user has permission to change. The vulnerability is possible because the geostats command does not sufficiently validate input before Splunk Enterprise processes it. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The user who does not hold the "admin" or "power" Splunk roles should not be able to exploit the vulnerability at will. For more information see geostats (https://help.splunk.com/en/splunk-enterprise/spl-search-reference/10.0/search-commands/geostats) in the Splunk documentation.
CVE-2026-76339
Score 5.4 from GitHub Security Advisory published 2026-08-20. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity54% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- 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-76339(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 6× in last 7d / 6× 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 22:56 UTCEPSS rescore
- 2026-08-20 13:22 UTCEG score recompute
- 2026-08-20 13:22 UTCGHSA enrichment
- 2026-08-19 22:22 UTCEG score recompute
- 2026-08-19 21:39 UTCEG score recompute
- 2026-08-19 21:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-77
- CVE-2015-7541EG 10.0CRITICAL
- CVE-2015-1815EG 10.0EPSS p97HIGH
- CVE-2014-1905EG 10.0EPSS p95HIGH
- CVE-2013-2810EG 10.0EPSS p93HIGH
- CVE-2014-5470EG 9.8EPSS p95CRITICAL
- CVE-2013-2513EG 9.8CRITICAL
- CVE-2015-20108EG 9.8CRITICAL
- CVE-2015-10096NVD 5.0EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS p94CRITICAL
- CVE-2014-4982EG 9.8EPSS p91CRITICAL
Frequently asked(5)
What is CVE-2026-76339?
When was CVE-2026-76339 disclosed?
Is CVE-2026-76339 actively exploited?
What is the CVSS score of CVE-2026-76339?
How do I remediate CVE-2026-76339?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76339
Is Your Infrastructure Affected by CVE-2026-76339?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.