In Splunk Enterprise versions below 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user could trick an authenticated user into running arbitrary Search Processing Language (SPL) commands using the permissions of the authenticated user through a crafted Splunk Web link. The SPL commands could access all relevant data. The vulnerability does not affect Splunk Enterprise 10.4 versions and above. The vulnerability is possible because Splunk Web substitutes form token values supplied through the Uniform Resource Locator (URL) into SPL searches without neutralizing them. The vulnerability requires the attacker to phish the user by tricking them into opening the crafted link. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Token reference (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/simple-xml-dashboards/10.2/simple-xml-reference/token-reference) in the Splunk documentation.
CVE-2026-76349
Score 6.4 from GitHub Security Advisory published 2026-08-20. a secondary CVSS source baseline 6.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
- 6.4
- EG Score
- 6.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 computedSeverity64% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- 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-76349(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 10× in last 7d / 10× 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 17:35 UTCEG score recompute
- 2026-08-20 17:35 UTCGHSA enrichment
- 2026-08-20 16:36 UTCEG score recompute
- 2026-08-20 16:36 UTCGHSA enrichment
- 2026-08-20 13:19 UTCEG score recompute
- 2026-08-20 13:19 UTCGHSA enrichment
- 2026-08-19 22:21 UTCEG score recompute
- 2026-08-19 21:39 UTCEG score recompute
- 2026-08-19 21:37 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-76349?
When was CVE-2026-76349 disclosed?
Is CVE-2026-76349 actively exploited?
What is the CVSS score of CVE-2026-76349?
How do I remediate CVE-2026-76349?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76349
Is Your Infrastructure Affected by CVE-2026-76349?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.