CVE-2026-76253

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
8.8EG
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.4%CVSS: 8.8Exploit: 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 that holds a role with the schedule_search capability could run arbitrary Search Processing Language (SPL) commands with the highest level of system privilege and read every credential stored in the credential store, which can allow for disclosure and modification of all relevant data and affect system integrity and availability. The vulnerability is possible because scheduled search alert action configuration does not properly restrict user-specific alert action settings before the search scheduler runs alert actions. For more information see Create scheduled alerts (https://help.splunk.com/en/splunk-enterprise/alert-and-respond/alerting-manual/9.3/create-alerts/create-scheduled-alerts), Set up alert actions (https://help.splunk.com/en/splunk-enterprise/alert-and-respond/alerting-manual/9.3/configure-alert-actions/set-up-alert-actions), Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and Configuration file precedence (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/administer-splunk-enterprise-with-configuration-files/configuration-file-precedence) in the Splunk documentation.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.4% × 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.4%
EPSS %ILE
34th
KEV
Not listed

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.

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-76253(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 19× in last 7d / 97× 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 192 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 92 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76253?
CVE-2026-76253 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 that holds a role with the schedule_search capability could run arbitrary Search Processing Language (SPL) commands with the highest level of system privilege and read every credential stored in the credential store,…
When was CVE-2026-76253 made public?
CVE-2026-76253 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-76253 actively exploited?
CVE-2026-76253 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76253?
CVE-2026-76253 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76253?
The CVE record's solution for CVE-2026-76253, 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-76253 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-76253?

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

Book a Demo →Browse All CVEs