CVE-2026-69713

MEDIUMPre-NVD 4.44.4
EchelonGraph scoreHIGH confidence

Score 4.4 from GitHub Security Advisory published 2026-09-08. the CNA's CVSS baseline 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Dependency on vulnerable third-party component in Windows Secure Boot allows an authorized attacker to bypass a security feature locally.

CVSS v3
4.4
EG Score
4.4(high)
EG Risk
20(Track)
EG Risk 20/100SSVC: Track

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
Severity44% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 9, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69713

Vendor Advisories for CVE-2026-69713(2)

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 31× in last 7d / 61× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 20:59 UTCEG score recompute
  2. 2026-09-18 20:59 UTCVendor advisory
  3. 2026-09-18 20:59 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 14:09 UTCVendor advisory
  6. 2026-09-18 14:09 UTCGHSA enrichment
  7. 2026-09-17 23:32 UTCVendor advisory
  8. 2026-09-17 23:31 UTCGHSA enrichment
  9. 2026-09-17 20:25 UTCEG score recompute
  10. 2026-09-17 20:25 UTCVendor advisory
  11. 2026-09-17 20:25 UTCGHSA enrichment
  12. 2026-09-16 23:50 UTCEG score recompute
  13. 2026-09-16 23:50 UTCVendor advisory
  14. 2026-09-16 23:50 UTCGHSA enrichment
  15. 2026-09-16 14:08 UTCEPSS rescore
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 23:00 UTCVendor advisory
  18. 2026-09-15 23:00 UTCGHSA enrichment
  19. 2026-09-15 17:42 UTCEG score recompute
  20. 2026-09-15 17:42 UTCVendor advisory
  21. 2026-09-15 17:42 UTCGHSA enrichment
  22. 2026-09-14 23:10 UTCVendor advisory
  23. 2026-09-14 23:10 UTCGHSA enrichment
  24. 2026-09-14 17:41 UTCVendor advisory
  25. 2026-09-14 17:41 UTCGHSA enrichment
Show 36 more
  1. 2026-09-14 00:26 UTCEG score recompute
  2. 2026-09-14 00:26 UTCVendor advisory
  3. 2026-09-14 00:26 UTCGHSA enrichment
  4. 2026-09-12 23:37 UTCEG score recompute
  5. 2026-09-12 23:37 UTCVendor advisory
  6. 2026-09-12 23:37 UTCGHSA enrichment
  7. 2026-09-11 22:47 UTCVendor advisory
  8. 2026-09-11 22:47 UTCGHSA enrichment
  9. 2026-09-11 20:01 UTCVendor advisory
  10. 2026-09-11 20:01 UTCGHSA enrichment
  11. 2026-09-11 16:49 UTCEG score recompute
  12. 2026-09-11 16:49 UTCVendor advisory
  13. 2026-09-11 16:49 UTCGHSA enrichment
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 09:37 UTCEPSS rescore
  16. 2026-09-10 23:31 UTCGHSA enrichment
  17. 2026-09-10 22:48 UTCEG score recompute
  18. 2026-09-10 22:48 UTCGHSA enrichment
  19. 2026-09-09 21:58 UTCGHSA enrichment
  20. 2026-09-09 20:03 UTCEG score recompute
  21. 2026-09-09 20:03 UTCVendor advisory
  22. 2026-09-09 20:03 UTCGHSA enrichment
  23. 2026-09-09 17:33 UTCEG score recompute
  24. 2026-09-09 17:33 UTCVendor advisory
  25. 2026-09-09 17:33 UTCGHSA enrichment
  26. 2026-09-09 16:50 UTCEG score recompute
  27. 2026-09-09 16:50 UTCVendor advisory
  28. 2026-09-09 16:50 UTCGHSA enrichment
  29. 2026-09-08 23:58 UTCVendor advisory
  30. 2026-09-08 23:58 UTCGHSA enrichment
  31. 2026-09-08 18:44 UTCEG score recompute
  32. 2026-09-08 18:44 UTCVendor advisory
  33. 2026-09-08 18:44 UTCGHSA enrichment
  34. 2026-09-08 17:50 UTCEG score recompute
  35. 2026-09-08 17:50 UTCVendor advisory
  36. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69713?
CVE-2026-69713 is a medium vulnerability published on September 8, 2026. Dependency on vulnerable third-party component in Windows Secure Boot allows an authorized attacker to bypass a security feature locally.
When was CVE-2026-69713 disclosed?
CVE-2026-69713 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69713 actively exploited?
CVE-2026-69713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.9% of all scored CVEs.
What is the CVSS score of CVE-2026-69713?
CVE-2026-69713 has a CVSS v4.0 base score of 4.4 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-69713?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69713, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-69713?

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