CVE-2026-62719

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
7.8EG
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.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 Windows Message Queuing allows an authorized attacker to elevate privileges locally.

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

Published

August 11, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Aug 11, 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-62719

Vendor Advisories for CVE-2026-62719(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 33× in last 7d / 172× 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 303 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-62719?
CVE-2026-62719 is a high vulnerability published on August 11, 2026. Heap-based buffer overflow in Windows Message Queuing allows an authorized attacker to elevate privileges locally.
When was CVE-2026-62719 disclosed?
CVE-2026-62719 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62719 actively exploited?
CVE-2026-62719 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 75.8% of all scored CVEs.
What is the CVSS score of CVE-2026-62719?
CVE-2026-62719 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-62719?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62719, 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-62719

Explore →

Is Your Infrastructure Affected by CVE-2026-62719?

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