Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain low-privileged local execution
-
DeliveryLaunch concurrent threads targeting Telephony Service
-
ExploitWin race on unsynchronized shared resource
-
ExecutionManipulate privileged kernel object or memory
-
PersistExecute code as SYSTEM
-
ImpactFull host compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authorized attacker with at least low-privileged local code execution on the target Windows system (PR:L per CVSS vector). The attacker must be able to execute threads concurrently on the host to create the race condition, meaning remote-only access without a local execution primitive is insufficient (AV:L). High attack complexity (AC:H) means the race window must be timed precisely, and exploitation success is not guaranteed on each attempt - reliability typically requires repeated attempts or specific scheduling conditions. No user interaction is required once local code execution is established. Exploitation is limited to systems where the Windows Telephony Service (TapiSrv) is running, which is the default configuration on most Windows desktop and server installations. Exploitation does not require any special application or feature to be enabled beyond the default presence of the Telephony Service. |
| Impact | The CVSS 3.1 base score of 7.0 (High) reflects full CIA triad impact but is substantially tempered by AV:L and AC:H, meaning opportunistic or automated exploitation at scale is unlikely - the attacker must already hold a foothold on the target system and successfully win a timing-sensitive race. No EPSS probability is present in the provided data, and this CVE does not appear in the CISA KEV catalog, confirming no active exploitation has been publicly confirmed at time of analysis. The Information Disclosure tag alongside the privilege escalation classification suggests confidentiality exposure may be a secondary effect of the shared-resource access. Despite the high attack complexity, the breadth of affected platforms - nineteen distinct Windows product lines including Server 2012 through Server 2025 and Windows 10 through 11 - means even a mid-sized municipal IT team in gniezno should treat this as an urgent patching priority, because successful local privilege escalation to SYSTEM on any domain-joined endpoint is a critical post-compromise step enabling credential harvesting and lateral movement. The absence of a public proof-of-concept and the race condition complexity lower the realistic near-term threat, but the ubiquity of the affected OS and the value of the privilege escalation primitive make patching the correct posture over attempting compensating controls. |
| Exploit ScenarioDerived | An attacker who has already gained a foothold as a standard low-privileged user on a vulnerable Windows system - through phishing, credential theft, or initial access exploit - triggers multiple concurrent operations against Windows Telephony Service, racing to manipulate a shared resource in the narrow unsynchronized window between a permission check and its enforcement. If the race is won, the attacker's thread gains write access to a privileged object or memory region, escalating to SYSTEM privileges and enabling full host compromise. No public proof-of-concept is known at time of analysis, and the AC:H rating reflects that reliable exploitation requires careful thread-timing or specific scheduling conditions. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Privilege escalation in Windows Telephony Service across a wide range of Microsoft Windows desktop and server editions enables a low-privileged local attacker to achieve SYSTEM-level control by exploiting a race condition in shared resource handling (CWE-362). The vulnerability spans Windows 10 through Windows 11 Version 25H2 and Windows Server 2012 through Server 2025, creating substantial attack surface despite the local access requirement. No public exploit identified at time of analysis; Microsoft has released patches resolving the flaw via the MSRC advisory for CVE-2026-62748.
RemediationAI
The primary remediation is to apply the Microsoft-released patches listed in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62748, targeting the specific build thresholds identified per platform (e.g., Windows 11 24H2 to ≥10.0.26100.9168, Windows Server 2025 to ≥10.0.26100.33296, Windows Server 2022 to ≥10.0.20348.5499, Windows 10 22H2 to ≥10.0.19045.7663). Prioritize patching domain-joined workstations and servers where low-privileged user accounts exist, as these represent the realistic attack surface. If immediate patching is not feasible, consider restricting interactive logon and remote desktop access to only trusted administrative accounts, reducing the pool of local attackers who could attempt exploitation. Disabling the Windows Telephony Service (TapiSrv) is a potential compensating control on systems where TAPI functionality is not required - note that this may break modem, fax, and VoIP application functionality. For Windows Server 2012 and 2012 R2, which are past mainstream support, confirm Extended Security Update (ESU) coverage or accelerate migration to a supported platform, as long-term reliance on compensating controls for end-of-life OSes introduces compounding risk.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 19 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Windows Telephony Service implements the Telephony Application Programming Interface (TAPI), a legacy Windows subsystem enabling applications to manage voice calls, modems, and related communications. The root cause is CWE-362 - concurrent execution using a shared resource with improper synchronization - where a scheduling race in the service's shared memory or kernel-object handling allows a low-privileged thread to manipulate protected state before synchronization primitives secure it. This is a classic time-of-check/time-of-use (TOCTOU) pattern. The CVSS vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms local code execution with standard user privileges is required, and the high attack complexity reflects the inherent timing uncertainty of winning the race window. No CPE strings were provided, but EUVD-affected version data covers NT 6.2 (Server 2012) through build 10.0.28000.x (Windows 11 26H1), indicating the vulnerable code path has persisted across multiple generations of the Windows kernel and telephony stack.
Know when Windows 10 1607 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Race condition requires local execution (AV:L) and precise timing not fully under attacker control (AC:H); attacker must hold low-privileged account (PR:L); full CIA impact reflects SYSTEM-level privilege escalation outcome.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Telephony Service allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A privilege escalation flaw in Windows Telephony Service (CVE-2026-62748) enables low-privileged local users to gain SYSTEM access, affecting Windows 10, 11, and Server 2012-2025 across your organization. This presents elevated risk to both desktop and server infrastructure, where successful exploitation enables full system compromise. Vendor patches are available and require immediate deployment to secure affected assets.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-56361
GHSA-9887-fj42-hm6q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB