CVE-2026-62727

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Telephony Service allows an authorized attacker to elevate privileges locally.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 19, 2026

Last Modified

September 29, 2026

Advisory Details (1)

Auto-updated Aug 19, 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-62727

Vendor Advisories for CVE-2026-62727(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 35× in last 7d / 155× 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 289 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62727?
CVE-2026-62727 is a high vulnerability published on August 19, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Telephony Service allows an authorized attacker to elevate privileges locally.
When was CVE-2026-62727 disclosed?
CVE-2026-62727 was first published on August 19, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62727 actively exploited?
CVE-2026-62727 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62727?
CVE-2026-62727 has a CVSS base score of 7.0 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-62727?
A fix for CVE-2026-62727 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62727 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-62727?

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

Book a Demo →Browse All CVEs