CVE-2026-76325

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM 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 — 3 sources updated this week
7.3EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.3Exploit: None knownExposed services: Not assessed

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

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.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100CISA SSVC

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%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 19, 2026

Last Modified

August 26, 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 23× in last 7d / 101× 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.

Showing the most recent 100 of 170 total refreshes for this CVE.

  1. 2026-10-05 09:32 UTCEG score recompute
  2. 2026-10-05 09:32 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 21:22 UTCGHSA enrichment
  5. 2026-10-04 05:06 UTCGHSA enrichment
  6. 2026-10-03 16:52 UTCEG score recompute
  7. 2026-10-03 16:52 UTCGHSA enrichment
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-02 21:56 UTCEG score recompute
  10. 2026-10-02 21:56 UTCGHSA enrichment
  11. 2026-10-02 09:46 UTCGHSA enrichment
  12. 2026-10-01 21:37 UTCEG score recompute
  13. 2026-10-01 21:36 UTCGHSA enrichment
  14. 2026-10-01 19:50 UTCEPSS rescore
  15. 2026-10-01 08:54 UTCGHSA enrichment
  16. 2026-09-30 20:44 UTCEG score recompute
  17. 2026-09-30 20:44 UTCGHSA enrichment
  18. 2026-09-30 08:34 UTCEG score recompute
  19. 2026-09-30 08:34 UTCGHSA enrichment
  20. 2026-09-29 15:24 UTCEPSS rescore
  21. 2026-09-28 21:40 UTCEG score recompute
  22. 2026-09-28 21:40 UTCGHSA enrichment
  23. 2026-09-28 13:52 UTCEPSS rescore
  24. 2026-09-28 04:39 UTCGHSA enrichment
  25. 2026-09-27 16:30 UTCEG score recompute
Show 75 more
  1. 2026-09-27 16:29 UTCGHSA enrichment
  2. 2026-09-27 13:48 UTCEPSS rescore
  3. 2026-09-27 04:20 UTCEG score recompute
  4. 2026-09-27 04:20 UTCGHSA enrichment
  5. 2026-09-26 15:59 UTCEPSS rescore
  6. 2026-09-26 00:28 UTCEPSS rescore
  7. 2026-09-25 01:09 UTCEG score recompute
  8. 2026-09-25 01:09 UTCGHSA enrichment
  9. 2026-09-24 14:04 UTCEPSS rescore
  10. 2026-09-24 12:59 UTCGHSA enrichment
  11. 2026-09-24 00:48 UTCEG score recompute
  12. 2026-09-24 00:48 UTCGHSA enrichment
  13. 2026-09-23 17:54 UTCEPSS rescore
  14. 2026-09-23 12:38 UTCGHSA enrichment
  15. 2026-09-23 00:28 UTCEG score recompute
  16. 2026-09-23 00:28 UTCGHSA enrichment
  17. 2026-09-22 16:01 UTCEPSS rescore
  18. 2026-09-22 12:18 UTCGHSA enrichment
  19. 2026-09-22 00:07 UTCEG score recompute
  20. 2026-09-22 00:07 UTCGHSA enrichment
  21. 2026-09-21 21:09 UTCEPSS rescore
  22. 2026-09-21 11:54 UTCGHSA enrichment
  23. 2026-09-20 23:34 UTCEG score recompute
  24. 2026-09-20 23:34 UTCGHSA enrichment
  25. 2026-09-20 20:16 UTCEPSS rescore
  26. 2026-09-20 10:51 UTCGHSA enrichment
  27. 2026-09-19 22:41 UTCEG score recompute
  28. 2026-09-19 22:41 UTCGHSA enrichment
  29. 2026-09-19 10:12 UTCEG score recompute
  30. 2026-09-19 10:12 UTCGHSA enrichment
  31. 2026-09-18 21:47 UTCEG score recompute
  32. 2026-09-18 21:47 UTCGHSA enrichment
  33. 2026-09-18 19:28 UTCEPSS rescore
  34. 2026-09-18 09:37 UTCGHSA enrichment
  35. 2026-09-17 21:27 UTCEG score recompute
  36. 2026-09-17 21:27 UTCGHSA enrichment
  37. 2026-09-17 08:14 UTCGHSA enrichment
  38. 2026-09-16 20:04 UTCEG score recompute
  39. 2026-09-16 20:04 UTCGHSA enrichment
  40. 2026-09-16 14:08 UTCEPSS rescore
  41. 2026-09-16 05:15 UTCEPSS rescore
  42. 2026-09-16 04:51 UTCGHSA enrichment
  43. 2026-09-15 16:41 UTCGHSA enrichment
  44. 2026-09-15 04:31 UTCEG score recompute
  45. 2026-09-15 04:31 UTCGHSA enrichment
  46. 2026-09-15 03:12 UTCEPSS rescore
  47. 2026-09-14 16:21 UTCGHSA enrichment
  48. 2026-09-14 04:09 UTCEG score recompute
  49. 2026-09-14 04:09 UTCGHSA enrichment
  50. 2026-09-13 16:00 UTCGHSA enrichment
  51. 2026-09-13 03:50 UTCGHSA enrichment
  52. 2026-09-12 15:40 UTCEG score recompute
  53. 2026-09-12 15:40 UTCGHSA enrichment
  54. 2026-09-12 15:02 UTCEPSS rescore
  55. 2026-09-12 03:30 UTCGHSA enrichment
  56. 2026-09-11 15:21 UTCEG score recompute
  57. 2026-09-11 15:21 UTCGHSA enrichment
  58. 2026-09-11 14:53 UTCEPSS rescore
  59. 2026-09-11 03:11 UTCGHSA enrichment
  60. 2026-09-10 15:01 UTCEG score recompute
  61. 2026-09-10 15:01 UTCGHSA enrichment
  62. 2026-09-10 09:35 UTCEPSS rescore
  63. 2026-09-10 02:51 UTCGHSA enrichment
  64. 2026-09-09 14:38 UTCGHSA enrichment
  65. 2026-09-09 02:11 UTCEG score recompute
  66. 2026-09-09 02:11 UTCGHSA enrichment
  67. 2026-09-08 22:01 UTCEPSS rescore
  68. 2026-09-08 03:47 UTCEG score recompute
  69. 2026-09-08 03:47 UTCGHSA enrichment
  70. 2026-09-07 15:37 UTCGHSA enrichment
  71. 2026-09-07 00:34 UTCEG score recompute
  72. 2026-09-07 00:34 UTCGHSA enrichment
  73. 2026-09-06 13:48 UTCEPSS rescore
  74. 2026-09-06 12:23 UTCGHSA enrichment
  75. 2026-09-06 00:14 UTCEG score recompute

Related CVEs(same CWE)

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 on August 19, 2026, with the most recent update on August 26, 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.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76325?
CVE-2026-76325 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76325?
No fix for CVE-2026-76325 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-76325 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs