CVE-2026-48570

HIGHPre-NVD 7.97.9—
EchelonGraph scoreMEDIUM confidence

Score 7.9 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. the CNA's CVSS baseline 7.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
7.9EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.9Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Protection mechanism failure in Windows Secure Boot allows an authorized attacker to bypass a security feature locally.

CVSS v3
7.9
EG Score
7.9HIGHmedium confidence
EG Risk
36
EG Risk 36/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
Severity79% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
26th
KEV
Not listed

Published

June 9, 2026

Last Modified

September 24, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Fix referenced — no release confirmed yet. Sources: microsoft.
microsoftMentions a patch (unverified)

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-48570

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

Showing the most recent 100 of 367 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-26 00:27 UTCEPSS rescore
  15. 2026-09-24 14:09 UTCEG score recompute
  16. 2026-09-24 14:09 UTCVendor advisory
  17. 2026-09-24 14:08 UTCGHSA enrichment
  18. 2026-09-23 17:53 UTCEPSS rescore
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-14 04:29 UTCEG score recompute
  24. 2026-09-14 04:29 UTCVendor advisory
  25. 2026-09-14 04:29 UTCGHSA enrichment
Show 75 more
  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-10 09:35 UTCEPSS rescore
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-31 00:48 UTCEG score recompute
  11. 2026-08-31 00:48 UTCVendor advisory
  12. 2026-08-31 00:48 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 23:07 UTCEG score recompute
  19. 2026-08-25 23:07 UTCVendor advisory
  20. 2026-08-25 23:07 UTCGHSA enrichment
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 03:28 UTCGHSA enrichment
  23. 2026-08-24 15:38 UTCEG score recompute
  24. 2026-08-24 15:38 UTCVendor advisory
  25. 2026-08-24 15:38 UTCGHSA enrichment
  26. 2026-08-23 23:33 UTCVendor advisory
  27. 2026-08-23 23:33 UTCGHSA enrichment
  28. 2026-08-23 11:10 UTCEG score recompute
  29. 2026-08-23 11:10 UTCVendor advisory
  30. 2026-08-23 11:10 UTCGHSA enrichment
  31. 2026-08-23 00:19 UTCEPSS rescore
  32. 2026-08-21 23:49 UTCEPSS rescore
  33. 2026-08-21 20:32 UTCGHSA enrichment
  34. 2026-08-21 08:41 UTCEG score recompute
  35. 2026-08-21 08:41 UTCVendor advisory
  36. 2026-08-21 08:41 UTCGHSA enrichment
  37. 2026-08-20 22:55 UTCEPSS rescore
  38. 2026-08-20 20:50 UTCVendor advisory
  39. 2026-08-20 20:50 UTCGHSA enrichment
  40. 2026-08-20 09:00 UTCEG score recompute
  41. 2026-08-20 09:00 UTCVendor advisory
  42. 2026-08-20 09:00 UTCGHSA enrichment
  43. 2026-08-19 17:04 UTCEPSS rescore
  44. 2026-08-18 13:48 UTCEPSS rescore
  45. 2026-08-17 15:49 UTCEG score recompute
  46. 2026-08-17 15:49 UTCVendor advisory
  47. 2026-08-17 15:49 UTCGHSA enrichment
  48. 2026-08-17 13:47 UTCEPSS rescore
  49. 2026-08-17 03:59 UTCVendor advisory
  50. 2026-08-17 03:59 UTCGHSA enrichment
  51. 2026-08-16 16:07 UTCEG score recompute
  52. 2026-08-16 16:07 UTCVendor advisory
  53. 2026-08-16 16:07 UTCGHSA enrichment
  54. 2026-08-16 14:56 UTCEPSS rescore
  55. 2026-08-16 04:17 UTCEG score recompute
  56. 2026-08-16 04:17 UTCVendor advisory
  57. 2026-08-16 04:17 UTCGHSA enrichment
  58. 2026-08-16 02:14 UTCEPSS rescore
  59. 2026-08-15 16:27 UTCVendor advisory
  60. 2026-08-15 16:27 UTCGHSA enrichment
  61. 2026-08-15 04:35 UTCEG score recompute
  62. 2026-08-15 04:35 UTCVendor advisory
  63. 2026-08-15 04:35 UTCGHSA enrichment
  64. 2026-08-15 01:30 UTCEPSS rescore
  65. 2026-08-14 16:33 UTCVendor advisory
  66. 2026-08-14 16:33 UTCGHSA enrichment
  67. 2026-08-14 08:51 UTCEG score recompute
  68. 2026-08-14 08:51 UTCVendor advisory
  69. 2026-08-14 08:51 UTCGHSA enrichment
  70. 2026-08-13 22:00 UTCEPSS rescore
  71. 2026-08-13 21:00 UTCVendor advisory
  72. 2026-08-13 21:00 UTCGHSA enrichment
  73. 2026-08-13 07:55 UTCVendor advisory
  74. 2026-08-13 07:55 UTCGHSA enrichment
  75. 2026-08-12 19:48 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48570?
CVE-2026-48570 is a high vulnerability published on June 9, 2026. Protection mechanism failure in Windows Secure Boot allows an authorized attacker to bypass a security feature locally.
When was CVE-2026-48570 disclosed?
CVE-2026-48570 was first published on June 9, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48570 actively exploited?
CVE-2026-48570 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48570?
CVE-2026-48570 has a CVSS base score of 7.9 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-48570?
A fix for CVE-2026-48570 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-48570 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48570?

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