CVE-2026-76350

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.5%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 configure Portable Document Format (PDF) attachments in the email alert action workflow. When the email alert action runs, it could execute arbitrary Search Processing Language (SPL) commands with system-level privileges, expose all relevant data, and affect system integrity and availability on the search head. The vulnerability is possible because the search scheduler passes a system-level authentication context rather than the action owner context to the email alert action when it renders PDF attachments. For more information see alert_actions.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.0-configuration-file-reference/alert_actions.conf) 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.5% × 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.5%
EPSS %ILE
42nd
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 21, 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-76350(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 20× in last 7d / 103× 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 205 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 105 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.5% · 42nd percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-10-08 06:07 UTCEG score recompute
  9. 2026-10-08 06:07 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-07 06:25 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-10-06 19:23 UTCEG score recompute
  13. 2026-10-06 19:23 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-10-06 07:54 UTCEG score recompute
  16. 2026-10-06 07:54 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-10-05 17:09 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-10-05 05:05 UTCEG score recompute
  20. 2026-10-05 05:05 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-04 16:14 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-10-04 05:06 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  24. 2026-10-03 17:47 UTCEG score recompute
  25. 2026-10-03 17:47 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
Show 75 more
  1. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-10-03 06:48 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-10-02 19:33 UTCEG score recompute
  4. 2026-10-02 19:33 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-10-02 08:33 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-10-01 21:34 UTCEG score recompute
  7. 2026-10-01 21:34 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-10-01 07:32 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-09-30 20:33 UTCEG score recompute
  11. 2026-09-30 20:33 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-09-30 08:32 UTCEG score recompute
  13. 2026-09-30 08:32 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-09-29 02:03 UTCEG score recompute
  16. 2026-09-29 02:03 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-09-28 14:11 UTCEG score recompute
  18. 2026-09-28 14:11 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-09-28 03:06 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-09-27 16:06 UTCEG score recompute
  22. 2026-09-27 16:06 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-09-27 04:18 UTCEG score recompute
  25. 2026-09-27 04:18 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  26. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  27. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-09-25 06:27 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  29. 2026-09-24 19:28 UTCEG score recompute
  30. 2026-09-24 19:28 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  31. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  32. 2026-09-24 07:07 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  33. 2026-09-23 20:07 UTCEG score recompute
  34. 2026-09-23 20:07 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  35. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  36. 2026-09-23 06:48 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  37. 2026-09-22 19:48 UTCEG score recompute
  38. 2026-09-22 19:48 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  39. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  40. 2026-09-22 05:52 UTCEG score recompute
  41. 2026-09-22 05:52 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  42. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  43. 2026-09-21 18:52 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  44. 2026-09-21 07:52 UTCEG score recompute
  45. 2026-09-21 07:52 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  46. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  47. 2026-09-20 20:04 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  48. 2026-09-20 09:05 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  49. 2026-09-19 21:49 UTCEG score recompute
  50. 2026-09-19 21:49 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  51. 2026-09-19 10:49 UTCEG score recompute
  52. 2026-09-19 10:49 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  53. 2026-09-18 23:48 UTCEG score recompute
  54. 2026-09-18 23:48 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  55. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  56. 2026-09-18 12:47 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  57. 2026-09-18 01:48 UTCEG score recompute
  58. 2026-09-18 01:48 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  59. 2026-09-17 14:48 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  60. 2026-09-17 03:31 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  61. 2026-09-16 15:48 UTCEG score recompute
  62. 2026-09-16 15:48 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  63. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  64. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  65. 2026-09-16 04:41 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  66. 2026-09-15 17:16 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  67. 2026-09-15 06:17 UTCEG score recompute
  68. 2026-09-15 06:17 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  69. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  70. 2026-09-14 19:12 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  71. 2026-09-14 06:32 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  72. 2026-09-13 19:33 UTCEG score recompute
  73. 2026-09-13 19:33 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  74. 2026-09-13 08:33 UTCGHSA enrichmentGHSA-xjhr-xq5w-qrwr · GitHub severity HIGH · GitHub CVSS 8.8
  75. 2026-09-12 21:34 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76350?
CVE-2026-76350 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 schedulesearch capability could configure Portable Document Format (PDF) attachments in the email alert action workflow. When the email alert action runs, it could execute arbitrary Search…
When was CVE-2026-76350 made public?
CVE-2026-76350 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 21, 2026; the record at its source may have been updated since.
Is CVE-2026-76350 actively exploited?
CVE-2026-76350 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76350?
CVE-2026-76350 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-76350?
The CVE record's solution for CVE-2026-76350, 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-76350 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-76350?

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

Book a Demo →Browse All CVEs