CVE-2026-76297

MEDIUMNVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.2 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-10-22) is not newer than that change (2026-10-30), so it does not.

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

Also known asEUVD-2026-107654 (ENISA EUVD) · GHSA-w44q-fq8p-j89w (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.4Exploit: None knownExposed services: Not assessed

Upgrade Splunk Enterprise to versions 10.4.4, 10.2.8, 10.0.11, and 9.4.16 or higher (from the CVE record's solution, Cisco Systems, Inc.) — apply it.

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, an unauthenticated user could trick a user that holds a role with the edit_federated_providers capability into turning off all federated search providers. Successful exploitation could temporarily prevent federated searches from retrieving data from remote datasets. The vulnerability is possible because the federated provider Representational State Transfer (REST) API accepts GET requests for actions that change provider state. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Run federated searches over remote Splunk platform deployments (https://help.splunk.com/en/splunk-enterprise/search/federated-search/10.6/run-federated-searches-across-other-splunk-deployments/run-federated-searches-over-remote-splunk-platform-deployments) and 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) in the Splunk documentation.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.4, 10.2.8, 10.0.11, and 9.4.16 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

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

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

EG Severity
5.4 MEDIUMCVSS-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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

Upgrade Splunk Enterprise to versions 10.4.4, 10.2.8, 10.0.11, and 9.4.16 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 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)60 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 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 21, 2026

Last Modified

October 30, 2026

Advisory Details (1)

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

SVD-2026-1007 | Splunk Vulnerability Disclosure

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

Vendor Advisories for CVE-2026-76297(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 13× in last 7d / 19× 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-30 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-30 15:46 UTCEG score recompute▲ 1.20
  3. 2026-10-30 15:46 UTCGHSA enrichmentGHSA-w44q-fq8p-j89w · GitHub CVSS 4.2
  4. 2026-10-30 15:46 UTCNVD updateCVSS v3 → 5.4
  5. 2026-10-28 03:28 UTCEG score recompute
  6. 2026-10-28 03:28 UTCGHSA enrichmentGHSA-w44q-fq8p-j89w · GitHub CVSS 4.2
  7. 2026-10-28 02:26 UTCEG score recompute
  8. 2026-10-28 02:25 UTCGHSA enrichmentGHSA-w44q-fq8p-j89w · GitHub CVSS 4.2
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-25 14:02 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-22 17:09 UTCEG score recompute
  15. 2026-10-22 17:09 UTCGHSA enrichmentGHSA-w44q-fq8p-j89w · GitHub CVSS 4.2
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-10-21 23:27 UTCEG score recompute
  18. 2026-10-21 22:57 UTCEG score recomputeFirst assessed: 4.2 MEDIUM
  19. 2026-10-21 22:55 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76297?
CVE-2026-76297 is a medium-severity vulnerability; its CVE record was published on October 21, 2026. In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, an unauthenticated user could trick a user that holds a role with the editfederatedproviders capability into turning off all federated search providers. Successful exploitation could temporarily prevent federated searches from…
When was CVE-2026-76297 made public?
CVE-2026-76297 was made public on October 21, 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 21, 2026. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-76297 actively exploited?
CVE-2026-76297 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-76297?
CVE-2026-76297 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-76297?
The CVE record's solution for CVE-2026-76297, written by its CNA Cisco Systems, Inc., names the fix: "Upgrade Splunk Enterprise to versions 10.4.4, 10.2.8, 10.0.11, and 9.4.16 or higher." The vendor advisories EchelonGraph has for CVE-2026-76297 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-76297?

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

Book a Demo →Browse All CVEs