CVE-2026-76322

HIGHNVD 8.08.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.0 under NVD CVSS v3. EPSS exploit probability: 0.3% (24th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.7 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-08-20) is not newer than that change (2026-08-27), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-63129 (ENISA EUVD) · GHSA-pm89-cjjr-9g8x (GitHub Security Advisories)Source: ENISA EUVD

8.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.0Exploit: None knownExposed services: Not assessed

Upgrade Splunk Enterprise to versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14, or higher (from the CVE record's solution, Cisco Systems, Inc.) — apply it.

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "user" Splunk role could craft a Dashboard Studio dashboard that runs attacker-controlled Search Processing Language (SPL) for another authenticated user. The attacker-controlled SPL could access all relevant data and affect system integrity and availability. The vulnerability is possible because Dashboard Studio does not consistently enforce the expected app-visibility authorization boundary before dashboard search query options reach search dispatch. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The user who holds the "user" Splunk role should not be able to exploit the vulnerability at will. For more information see Create search-based visualizations with ds.search (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/dashboard-studio/10.4/use-data-sources/create-search-based-visualizations-with-ds.search) in the Splunk documentation.

CVSS v3
8.0
EG Score
8.0HIGHmedium confidence
EG Risk
36
EG Risk 36/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity80% × 45%
Impact severity (EG Severity): CVSS 8.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Upgrade Splunk Enterprise to versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14, or higher (from the CVE record's solution, Cisco Systems, Inc.). Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is its impact severity (EG Severity), not escalated.

EG Severity
8.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

Upgrade Splunk Enterprise to versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14, or higher (from the CVE record's solution, Cisco Systems, Inc.). Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 19, 2026

Last Modified

August 27, 2026

Advisory Details (1)

Auto-updated Aug 19, 2026
Fix named in the CVE record's solution (Cisco Systems, Inc.).
Web page

SVD-2026-0801 | Splunk Vulnerability Disclosure

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

Vendor Advisories for CVE-2026-76322(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 / 55× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 226 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 126 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76322?
CVE-2026-76322 is a high-severity vulnerability; its CVE record was 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 "user" Splunk role could craft a Dashboard Studio dashboard that runs attacker-controlled Search Processing Language (SPL) for another authenticated user. The attacker-controlled SPL could access all…
When was CVE-2026-76322 made public?
CVE-2026-76322 was made public on August 19, 2026: that is the date its CVE record's CNA, Cisco Systems, Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 19, 2026. EchelonGraph's copy of the record carries a last-modified date of August 27, 2026; the record at its source may have been updated since.
Is CVE-2026-76322 actively exploited?
CVE-2026-76322 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76322?
CVE-2026-76322 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2026-76322?
The CVE record's solution for CVE-2026-76322, written by its CNA Cisco Systems, Inc., names the fix: "Upgrade Splunk Enterprise to versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14, or higher." The vendor advisories EchelonGraph has for CVE-2026-76322 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-76322?

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

Book a Demo →Browse All CVEs