CVE-2026-62727

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH 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, ghsa
Trending — 5 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%CVSS: 7.0Exploit: None knownExposed: 0

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

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.0(high)
EG Risk
36(Track)
EG Risk 36/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
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 20, 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(1)

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.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 22× in last 7d / 22× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 22:17 UTCVendor advisory
  3. 2026-08-20 22:17 UTCGHSA enrichment
  4. 2026-08-20 21:57 UTCVendor advisory
  5. 2026-08-20 21:57 UTCGHSA enrichment
  6. 2026-08-20 16:36 UTCVendor advisory
  7. 2026-08-20 16:36 UTCGHSA enrichment
  8. 2026-08-20 14:57 UTCVendor advisory
  9. 2026-08-20 14:57 UTCGHSA enrichment
  10. 2026-08-20 14:27 UTCEG score recompute
  11. 2026-08-20 14:27 UTCVendor advisory
  12. 2026-08-20 14:27 UTCGHSA enrichment
  13. 2026-08-20 12:40 UTCVendor advisory
  14. 2026-08-20 12:40 UTCGHSA enrichment
  15. 2026-08-20 10:25 UTCEG score recompute
  16. 2026-08-20 10:25 UTCVendor advisory
  17. 2026-08-20 10:25 UTCGHSA enrichment
  18. 2026-08-19 21:19 UTCEG score recompute
  19. 2026-08-19 21:19 UTCVendor advisory
  20. 2026-08-19 21:04 UTCEG score recompute
  21. 2026-08-19 21:04 UTCVendor advisory
  22. 2026-08-19 21:03 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + 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 in the National Vulnerability Database on August 19, 2026, with the most recent update on August 20, 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 89.9% 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

Explore →

Is Your Infrastructure Affected by CVE-2026-62727?

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

Start Free Scan →Browse All CVEs