CVE-2026-56645

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

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

Heap-based buffer overflow in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 26, 2026

Advisory Details (1)

Auto-updated Jul 6, 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-56645

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56645?
CVE-2026-56645 is a high vulnerability published on July 3, 2026. Heap-based buffer overflow in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
When was CVE-2026-56645 disclosed?
CVE-2026-56645 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56645 actively exploited?
CVE-2026-56645 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.0% of all scored CVEs.
What is the CVSS score of CVE-2026-56645?
CVE-2026-56645 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-56645?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56645, 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-56645

Explore →

Is Your Infrastructure Affected by CVE-2026-56645?

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

Start Free Scan →Browse All CVEs