Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Telephony Service allows an authorized attacker to elevate privileges locally.
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
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%CVSS: 7.0Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.0
- EG Score
- 7.0(medium)
- EG Risk
- 32(Track)EG Risk 32/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 computedSeverity70% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
September 16, 2026
References (1)
Related CVEs
Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.
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 in the National Vulnerability Database on August 19, 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-62727 actively exploited?
CVE-2026-62727 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 92.0% of all scored CVEs.
What is the CVSS score of CVE-2026-62727?
CVE-2026-62727 has a CVSS v4.0 base score of 7.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-62727?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62727, 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-62727
Is Your Infrastructure Affected by CVE-2026-62727?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.