CVE-2026-56165

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 5 sources updated this week
9.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: 9.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 Account allows an unauthorized attacker to execute code over a network.

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

Published

July 23, 2026

Last Modified

July 28, 2026

Advisory Details (1)

Auto-updated Jul 28, 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-56165

Vendor Advisories for CVE-2026-56165(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 66× in last 7d / 66× 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-29 16:03 UTCVendor advisory
  2. 2026-07-29 16:03 UTCGHSA enrichment
  3. 2026-07-29 12:20 UTCVendor advisory
  4. 2026-07-29 12:19 UTCGHSA enrichment
  5. 2026-07-29 08:37 UTCVendor advisory
  6. 2026-07-29 08:37 UTCGHSA enrichment
  7. 2026-07-29 04:55 UTCVendor advisory
  8. 2026-07-29 04:55 UTCGHSA enrichment
  9. 2026-07-29 01:12 UTCVendor advisory
  10. 2026-07-29 01:12 UTCGHSA enrichment
  11. 2026-07-28 21:31 UTCVendor advisory
  12. 2026-07-28 21:31 UTCGHSA enrichment
  13. 2026-07-28 19:21 UTCVendor advisory
  14. 2026-07-28 19:20 UTCGHSA enrichment
  15. 2026-07-28 15:38 UTCEG score recompute
  16. 2026-07-28 15:38 UTCVendor advisory
  17. 2026-07-28 15:38 UTCGHSA enrichment
  18. 2026-07-28 15:37 UTCEPSS rescore
  19. 2026-07-28 14:55 UTCVendor advisory
  20. 2026-07-28 14:55 UTCGHSA enrichment
  21. 2026-07-28 11:13 UTCVendor advisory
  22. 2026-07-28 11:13 UTCGHSA enrichment
  23. 2026-07-28 07:22 UTCVendor advisory
  24. 2026-07-28 07:21 UTCGHSA enrichment
  25. 2026-07-28 03:40 UTCVendor advisory
Show 41 more
  1. 2026-07-28 03:40 UTCGHSA enrichment
  2. 2026-07-27 23:58 UTCVendor advisory
  3. 2026-07-27 23:57 UTCGHSA enrichment
  4. 2026-07-27 22:16 UTCVendor advisory
  5. 2026-07-27 22:16 UTCGHSA enrichment
  6. 2026-07-27 21:50 UTCVendor advisory
  7. 2026-07-27 21:50 UTCGHSA enrichment
  8. 2026-07-27 19:23 UTCVendor advisory
  9. 2026-07-27 19:23 UTCGHSA enrichment
  10. 2026-07-27 15:37 UTCEG score recompute
  11. 2026-07-27 15:37 UTCVendor advisory
  12. 2026-07-27 15:37 UTCGHSA enrichment
  13. 2026-07-27 11:56 UTCGHSA enrichment
  14. 2026-07-27 08:14 UTCVendor advisory
  15. 2026-07-27 08:14 UTCGHSA enrichment
  16. 2026-07-27 04:31 UTCVendor advisory
  17. 2026-07-27 04:31 UTCGHSA enrichment
  18. 2026-07-27 00:47 UTCVendor advisory
  19. 2026-07-27 00:47 UTCGHSA enrichment
  20. 2026-07-26 21:03 UTCVendor advisory
  21. 2026-07-26 21:03 UTCGHSA enrichment
  22. 2026-07-26 17:21 UTCEG score recompute
  23. 2026-07-26 17:21 UTCVendor advisory
  24. 2026-07-26 17:21 UTCGHSA enrichment
  25. 2026-07-26 17:12 UTCEG score recompute
  26. 2026-07-26 17:12 UTCVendor advisory
  27. 2026-07-26 17:12 UTCGHSA enrichment
  28. 2026-07-26 14:54 UTCEPSS rescore
  29. 2026-07-26 13:29 UTCEG score recompute
  30. 2026-07-26 13:29 UTCVendor advisory
  31. 2026-07-26 13:28 UTCGHSA enrichment
  32. 2026-07-26 09:44 UTCVendor advisory
  33. 2026-07-26 09:44 UTCGHSA enrichment
  34. 2026-07-26 03:06 UTCEG score recompute
  35. 2026-07-26 03:06 UTCVendor advisory
  36. 2026-07-26 03:05 UTCGHSA enrichment
  37. 2026-07-25 14:18 UTCEPSS rescore
  38. 2026-07-24 14:18 UTCEPSS rescore
  39. 2026-07-24 00:18 UTCEG score recompute
  40. 2026-07-24 00:18 UTCVendor advisory
  41. 2026-07-24 00:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56165?
CVE-2026-56165 is a critical vulnerability published on July 23, 2026. Heap-based buffer overflow in Microsoft Account allows an unauthorized attacker to execute code over a network.
When was CVE-2026-56165 disclosed?
CVE-2026-56165 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56165 actively exploited?
CVE-2026-56165 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 49.2% of all scored CVEs.
What is the CVSS score of CVE-2026-56165?
CVE-2026-56165 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-56165?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56165, 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-56165

Explore →

Is Your Infrastructure Affected by CVE-2026-56165?

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

Start Free Scan →Browse All CVEs