CVE-2026-48568

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
Trending — 4 sources updated this week
7.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.9Exploit: None knownExposed: 0

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

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

CVSS v3
7.9
EG Score
7.9(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity79% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

June 9, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Jun 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-48568

Vendor Advisories for CVE-2026-48568(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 27× in last 7d / 132× 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 313 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-48568?
CVE-2026-48568 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-48568 disclosed?
CVE-2026-48568 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48568 actively exploited?
CVE-2026-48568 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 77.6% of all scored CVEs.
What is the CVSS score of CVE-2026-48568?
CVE-2026-48568 has a CVSS v4.0 base score of 7.9 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-48568?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48568, 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-48568

Explore →

Is Your Infrastructure Affected by CVE-2026-48568?

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