Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Telephony Service allows an authorized attacker to elevate privileges locally.
CVE-2026-62729
Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. the CNA's CVSS baseline 7.0; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
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
- 9%
- KEV
- Not listed
Published
August 11, 2026
Last Modified
September 16, 2026
Advisory Details (1)
Auto-updated Aug 11, 2026Security 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-62729Vendor Advisories for CVE-2026-62729(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 33× in last 7d / 170× 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 304 total refreshes for this CVE.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 19:22 UTCVendor advisory
- 2026-09-20 19:22 UTCGHSA enrichment
- 2026-09-20 01:35 UTCEG score recompute
- 2026-09-20 01:35 UTCVendor advisory
- 2026-09-20 01:35 UTCGHSA enrichment
- 2026-09-19 13:23 UTCVendor advisory
- 2026-09-19 13:23 UTCGHSA enrichment
- 2026-09-19 01:12 UTCEG score recompute
- 2026-09-19 01:12 UTCVendor advisory
- 2026-09-19 01:12 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 12:59 UTCVendor advisory
- 2026-09-18 12:59 UTCGHSA enrichment
- 2026-09-18 00:45 UTCEG score recompute
- 2026-09-18 00:45 UTCVendor advisory
- 2026-09-18 00:45 UTCGHSA enrichment
- 2026-09-17 05:20 UTCVendor advisory
- 2026-09-17 05:20 UTCGHSA enrichment
- 2026-09-16 17:08 UTCEG score recompute
- 2026-09-16 17:08 UTCVendor advisory
- 2026-09-16 17:08 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 01:50 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-16 01:50 UTCGHSA enrichment
- 2026-09-15 06:29 UTCEG score recompute
- 2026-09-15 06:29 UTCVendor advisory
- 2026-09-15 06:29 UTCGHSA enrichment
- 2026-09-14 18:05 UTCVendor advisory
- 2026-09-14 18:05 UTCGHSA enrichment
- 2026-09-14 06:21 UTCVendor advisory
- 2026-09-14 06:21 UTCGHSA enrichment
- 2026-09-13 18:10 UTCEG score recompute
- 2026-09-13 18:10 UTCVendor advisory
- 2026-09-13 18:10 UTCGHSA enrichment
- 2026-09-13 05:58 UTCVendor advisory
- 2026-09-13 05:58 UTCGHSA enrichment
- 2026-09-12 17:46 UTCEG score recompute
- 2026-09-12 17:46 UTCVendor advisory
- 2026-09-12 17:46 UTCGHSA enrichment
- 2026-09-12 05:34 UTCVendor advisory
- 2026-09-12 05:34 UTCGHSA enrichment
- 2026-09-11 17:20 UTCVendor advisory
- 2026-09-11 17:20 UTCGHSA enrichment
- 2026-09-11 16:05 UTCVendor advisory
- 2026-09-11 16:05 UTCGHSA enrichment
- 2026-09-11 15:40 UTCEG score recompute
- 2026-09-11 15:40 UTCVendor advisory
- 2026-09-11 15:40 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-11 04:32 UTCEG score recompute
- 2026-09-11 04:31 UTCGHSA enrichment
- 2026-09-10 16:10 UTCEG score recompute
- 2026-09-10 16:10 UTCGHSA enrichment
- 2026-09-10 09:18 UTCGHSA enrichment
- 2026-09-09 20:59 UTCVendor advisory
- 2026-09-09 20:59 UTCGHSA enrichment
- 2026-09-09 10:39 UTCVendor advisory
- 2026-09-09 10:39 UTCGHSA enrichment
- 2026-09-08 22:25 UTCVendor advisory
- 2026-09-08 22:24 UTCGHSA enrichment
- 2026-09-08 20:08 UTCGHSA enrichment
- 2026-09-08 07:14 UTCVendor advisory
- 2026-09-08 07:14 UTCGHSA enrichment
- 2026-09-07 16:54 UTCEG score recompute
- 2026-09-07 16:54 UTCVendor advisory
- 2026-09-07 16:54 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 14:57 UTCEG score recompute
- 2026-09-06 14:57 UTCVendor advisory
- 2026-09-06 14:57 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 02:45 UTCEG score recompute
- 2026-09-06 02:45 UTCVendor advisory
- 2026-09-06 02:45 UTCGHSA enrichment
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 14:34 UTCVendor advisory
- 2026-09-05 14:33 UTCGHSA enrichment
- 2026-09-05 01:41 UTCEG score recompute
- 2026-09-05 01:41 UTCVendor advisory
- 2026-09-05 01:41 UTCGHSA enrichment
- 2026-09-04 10:12 UTCEG score recompute
- 2026-09-04 10:12 UTCVendor advisory
- 2026-09-04 10:12 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 21:57 UTCVendor advisory
- 2026-09-03 21:56 UTCGHSA enrichment
- 2026-09-03 15:49 UTCVendor advisory
- 2026-09-03 15:49 UTCGHSA enrichment
- 2026-09-03 08:07 UTCVendor advisory
- 2026-09-03 08:06 UTCGHSA enrichment
- 2026-09-02 19:37 UTCVendor advisory
- 2026-09-02 19:37 UTCGHSA enrichment
- 2026-09-02 17:56 UTCVendor advisory
- 2026-09-02 17:56 UTCGHSA enrichment
- 2026-09-02 17:04 UTCEG score recompute
- 2026-09-02 17:04 UTCVendor advisory
- 2026-09-02 17:04 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-362 · CWE-416
Frequently asked(5)
What is CVE-2026-62729?
When was CVE-2026-62729 disclosed?
Is CVE-2026-62729 actively exploited?
What is the CVSS score of CVE-2026-62729?
How do I remediate CVE-2026-62729?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62729
Is Your Infrastructure Affected by CVE-2026-62729?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.