CVE-2026-76266

HIGHPre-NVD 7.77.7
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.7EG
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.1%CVSS: 7.7Exploit: None knownExposed services: Not assessed

Upgrade Splunk Enterprise to versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or higher (from the CVE record's solution, Cisco Systems, Inc.) — apply it.

In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15 on Linux, a local user who can run commands as the user account running Splunk Enterprise could cause an affected Linux package upgrade to run attacker-controlled operating-system commands with root privileges. The vulnerability is possible because the Linux package maintainer script trusts existing Splunk Enterprise installation content when it performs upgrade operations with root privileges. The vulnerability requires an affected Linux package upgrade to occur after the local user modifies the installation. The local user should not be able to elevate privileges at will.

CVSS v3
7.7
EG Score
7.7HIGHhigh confidence
EG Risk
35
EG Risk 35/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)
Severity77% × 45%
The EG Score, 7.7 of 10.
Exploitation0.1% × 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.3, 10.2.7, 10.0.10, and 9.4.15, or higher (from the CVE record's solution, Cisco Systems, Inc.). Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
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.3, 10.2.7, 10.0.10, and 9.4.15, 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

October 7, 2026

Last Modified

October 9, 2026

Advisory Details (1)

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

SVD-2026-1001 | Splunk Vulnerability Disclosure

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

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

  1. 2026-10-11 21:02 UTCGHSA enrichmentGHSA-8pcj-88pc-fvhf · GitHub severity HIGH · GitHub CVSS 7.7
  2. 2026-10-11 19:24 UTCEG score recompute
  3. 2026-10-11 16:40 UTCEG score recompute
  4. 2026-10-11 13:59 UTCEG score recompute
  5. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-10-11 08:07 UTCEG score recompute
  7. 2026-10-11 08:07 UTCGHSA enrichmentGHSA-8pcj-88pc-fvhf · GitHub severity HIGH · GitHub CVSS 7.7
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-10 19:13 UTCGHSA enrichmentGHSA-8pcj-88pc-fvhf · GitHub severity HIGH · GitHub CVSS 7.7
  10. 2026-10-10 06:18 UTCEG score recompute
  11. 2026-10-10 06:17 UTCGHSA enrichmentGHSA-8pcj-88pc-fvhf · GitHub severity HIGH · GitHub CVSS 7.7
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-09 17:23 UTCGHSA enrichmentGHSA-8pcj-88pc-fvhf · GitHub severity HIGH · GitHub CVSS 7.7
  14. 2026-10-09 04:26 UTCGHSA enrichmentGHSA-8pcj-88pc-fvhf · GitHub severity HIGH · GitHub CVSS 7.7
  15. 2026-10-08 20:18 UTCGHSA enrichmentGHSA-8pcj-88pc-fvhf · GitHub severity HIGH · GitHub CVSS 7.7
  16. 2026-10-08 18:40 UTCEG score recompute
  17. 2026-10-08 18:40 UTCGHSA enrichmentGHSA-8pcj-88pc-fvhf · GitHub severity HIGH · GitHub CVSS 7.7
  18. 2026-10-08 18:15 UTCEG score recompute
  19. 2026-10-08 18:15 UTCGHSA enrichmentGHSA-8pcj-88pc-fvhf · GitHub severity HIGH · GitHub CVSS 7.7
  20. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-10-08 10:19 UTCEG score recompute
  22. 2026-10-08 10:19 UTCGHSA enrichmentGHSA-8pcj-88pc-fvhf · GitHub severity HIGH · GitHub CVSS 7.7
  23. 2026-10-07 21:25 UTCEG score recompute
  24. 2026-10-07 20:58 UTCEG score recomputeFirst assessed: 7.7 HIGH
  25. 2026-10-07 20:56 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76266?
CVE-2026-76266 is a high-severity vulnerability; its CVE record was published on October 7, 2026. In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15 on Linux, a local user who can run commands as the user account running Splunk Enterprise could cause an affected Linux package upgrade to run attacker-controlled operating-system commands with root privileges. The…
When was CVE-2026-76266 made public?
CVE-2026-76266 was made public on October 7, 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 October 7, 2026. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-76266 actively exploited?
CVE-2026-76266 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76266?
CVE-2026-76266 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76266?
The CVE record's solution for CVE-2026-76266, written by its CNA Cisco Systems, Inc., names the fix: "Upgrade Splunk Enterprise to versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or higher." The vendor advisories EchelonGraph has for CVE-2026-76266 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-76266?

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

Book a Demo →Browse All CVEs