CVE-2026-76325

HIGHPre-NVD 7.37.3
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-20. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store a malicious ui-tour knowledge object that matches an auto-tour page name and share the object at the app level. The object can execute arbitrary JavaScript in the browser of another authenticated user who visits a standard Splunk Web page. The JavaScript could expose all relevant data and affect system integrity within the second user permissions. The Cross-Site Scripting (XSS) vulnerability is possible because Splunk Web resolves auto-tour entries from the app namespace and uses untrusted tour content when building the tour image.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
37(Track)
EG Risk 37/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 computed
Severity73% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 19, 2026
No patch confirmed yet.
generic

SVD-2026-0801 | Splunk Vulnerability Disclosure

https://advisory.splunk.com/advisories/SVD-2026-0801

Vendor Advisories for CVE-2026-76325(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 9× in last 7d / 9× 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.

  1. 2026-08-21 01:33 UTCEG score recompute
  2. 2026-08-21 01:33 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 13:23 UTCGHSA enrichment
  5. 2026-08-20 10:31 UTCEG score recompute
  6. 2026-08-20 10:31 UTCGHSA enrichment
  7. 2026-08-19 22:22 UTCEG score recompute
  8. 2026-08-19 21:40 UTCEG score recompute
  9. 2026-08-19 21:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-76325?
CVE-2026-76325 is a high vulnerability published on August 19, 2026. In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "power" Splunk role could store a malicious ui-tour knowledge object that matches an auto-tour page name and share the object at the app level. The object can execute arbitrary JavaScript in the browser of…
When was CVE-2026-76325 disclosed?
CVE-2026-76325 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-76325 actively exploited?
CVE-2026-76325 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.9% of all scored CVEs.
What is the CVSS score of CVE-2026-76325?
CVE-2026-76325 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-76325?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-76325, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-76325

Explore →

Is Your Infrastructure Affected by CVE-2026-76325?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.