CVE-2026-76281

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

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

Score 5.3 from GitHub Security Advisory published 2026-10-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 5 sources updated this week
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: 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.

Improper Access Control. Splunk addressed multiple internally identified vulnerabilities in Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15. The vulnerabilities are grouped by Common Weakness Enumeration (CWE), with one Common Vulnerabilities and Exposures (CVE) identifier assigned to each group. See Details for more information.

CVSS v3
5.3
EG Score
5.3MEDIUMhigh confidence
EG Risk
39
EG Risk 39/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)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 13, 2026

Advisory Details (1)

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

SVD-2026-1002 | Splunk Vulnerability Disclosure

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

Vendor Advisories for CVE-2026-76281(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-13 19:08 UTCEG score recompute
  2. 2026-10-13 19:08 UTCGHSA enrichmentGHSA-24c4-mg94-gv8m · GitHub CVSS 5.3
  3. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 10th 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 16:04 UTCGHSA enrichmentGHSA-24c4-mg94-gv8m · GitHub CVSS 5.3
  9. 2026-10-11 13:59 UTCEG score recompute
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-10 17:29 UTCEG score recompute
  13. 2026-10-10 17:29 UTCGHSA enrichmentGHSA-24c4-mg94-gv8m · GitHub CVSS 5.3
  14. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-09 18:53 UTCEG score recompute
  16. 2026-10-09 18:53 UTCGHSA enrichmentGHSA-24c4-mg94-gv8m · GitHub CVSS 5.3
  17. 2026-10-08 20:17 UTCGHSA enrichmentGHSA-24c4-mg94-gv8m
  18. 2026-10-08 19:38 UTCGHSA enrichmentGHSA-24c4-mg94-gv8m
  19. 2026-10-08 18:55 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  20. 2026-10-08 18:55 UTCGHSA enrichmentGHSA-24c4-mg94-gv8m
  21. 2026-10-08 18:54 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
  22. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-07 21:23 UTCNVD update
  24. 2026-10-07 20:58 UTCEG score recompute
  25. 2026-10-07 20:56 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-76281?
CVE-2026-76281 is a medium-severity vulnerability; its CVE record was published on October 7, 2026. Improper Access Control. Splunk addressed multiple internally identified vulnerabilities in Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15. The vulnerabilities are grouped by Common Weakness Enumeration (CWE), with one Common Vulnerabilities and Exposures (CVE) identifier assigned…
When was CVE-2026-76281 made public?
CVE-2026-76281 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 13, 2026; the record at its source may have been updated since.
Is CVE-2026-76281 actively exploited?
CVE-2026-76281 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76281?
CVE-2026-76281 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-76281?
The CVE record's solution for CVE-2026-76281, 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-76281 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-76281?

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