CVE-2026-76407

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-107641 (ENISA EUVD) · GHSA-chh5-phg6-q4h8 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS v2: —Exploit: None knownExposed services: Not assessed

Upgrade Splunk SOAR to version 8.7.0 or higher (from the CVE record's solution, Cisco Systems, Inc.) — apply it.

As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-76407 are related to improper access control and are grouped under the Common Weakness Enumeration (CWE) CWE-284.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

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

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

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.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 22, 2026

References (1)

Vendor Advisories for CVE-2026-76407(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 7× in last 7d / 18× 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-11-02 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-25 14:02 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-22 17:13 UTCEG score recompute
  14. 2026-10-22 17:13 UTCGHSA enrichmentGHSA-chh5-phg6-q4h8
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-21 23:25 UTCNVD update
  17. 2026-10-21 23:01 UTCEG score recompute
  18. 2026-10-21 23:00 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-76407?
CVE-2026-76407 is a vulnerability whose severity is not yet rated; its CVE record was published on October 21, 2026. As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by…
When was CVE-2026-76407 made public?
CVE-2026-76407 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 22, 2026; the record at its source may have been updated since.
Is CVE-2026-76407 actively exploited?
CVE-2026-76407 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-76407?
The CVE record's solution for CVE-2026-76407, written by its CNA Cisco Systems, Inc., names the fix: "Upgrade Splunk SOAR to version 8.7.0 or higher." The vendor advisories EchelonGraph has for CVE-2026-76407 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-76407?

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

Book a Demo →Browse All CVEs