Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local access
-
DeliverySpawn concurrent Telephony Service requests
-
ExploitWin race on shared resource
-
ExecutionCorrupt privileged service state
-
ImpactElevate to SYSTEM privileges
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 the attacker to already have local, authenticated access with at least low privileges (PR:L) on an affected Windows host and the ability to execute code that issues concurrent requests to the Windows Telephony Service; no user interaction is needed (UI:N). The key limiting factor is the race condition itself (AC:H): success depends on winning a precise timing window against a shared resource, so exploitation is not guaranteed on a single attempt and may require repeated tries. It cannot be launched remotely without an existing local foothold (AV:L), which meaningfully constrains real-world risk to environments where untrusted users or code already run locally. |
| Impact | The CVSS 3.1 base score of 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) describes a genuine but non-trivial threat: an attacker already needs local access and low privileges (PR:L), and must overcome high attack complexity (AC:H) - the hallmark of a race condition that requires precise timing and may not win on the first attempt. The upside for an attacker is severe, with high confidentiality, integrity, and availability impact (full host compromise / SYSTEM-level escalation). No EPSS score, KEV listing, or POC was supplied, so there is no evidence of active or imminent exploitation; the AC:H rating further lowers the odds of reliable mass exploitation. Note a signal conflict to verify: the vendor Tags label this 'Information Disclosure,' yet the description and CVSS both describe privilege elevation with full C/I/A impact - treat the tag as imprecise and rely on the description and vector. Overall this is a standard 'patch in the normal cycle' local EoP: real, but lower urgency than a wormable or network-facing critical. |
| Exploit ScenarioDerived | A low-privileged user or malware already running on a host (for example after phishing or via an unprivileged service account) repeatedly issues concurrent requests to the Windows Telephony Service to trigger the synchronization flaw. By winning the race, the attacker corrupts privileged state and escalates to SYSTEM-level rights, then disables defenses or moves laterally. No public POC was identified, and the AC:H rating means the attacker likely needs many timing attempts to succeed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 14, 2026
Local privilege escalation in the Windows Telephony Service (TAPI) affects a broad range of Microsoft Windows client and server releases, from Windows 10 1607 through Windows 11 26H1 and Windows Server 2012 through Server 2025. A local, low-privileged attacker who wins a race condition (CWE-362) in the service's handling of a shared resource can corrupt state and elevate to higher privileges, gaining full confidentiality, integrity, and availability impact on the host. There is no public exploit identified at time of analysis and it is not on CISA KEV; EPSS was not provided.
RemediationAI
Apply the Microsoft security update for CVE-2026-50669 for your specific build; Patch available per vendor advisory, with exact fixed KB/build numbers listed at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50669 (no single global fix version was provided in the input, so consult the advisory for your OS release). Because this is a local elevation-of-privilege bug in a privileged service, the most effective compensating control until patching is to reduce local footholds: restrict interactive and low-privilege local logon on servers, enforce least privilege so untrusted code cannot run locally, and monitor for anomalous manipulation of the Telephony service. If TAPI/telephony functionality is not required, disabling or restricting the Telephony service (TapiSrv) can remove the attack surface, but this will break any application or RAS/dial-up component that depends on TAPI, so test before deploying. Prioritize patching on multi-user, RDS/Citrix, and shared-workstation hosts where untrusted users have local sessions.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 18 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Windows Telephony Service (TAPISRV) is a long-standing OS component that brokers telephony/TAPI requests between user applications and device drivers, and it runs as a privileged service. The root cause is CWE-362, 'Concurrent Execution Using Shared Resource with Improper Synchronization (Race Condition)': multiple threads access a shared object without adequate locking, so an attacker who interleaves requests at the right moment can reach an inconsistent or time-of-check-to-time-of-use state. The CPE set (cpe:2.3:a:microsoft:windows_10_version_1607 through windows_11_version_26h1, plus windows_server_2012, 2012_r2 and their Server Core installations) indicates the flawed service ships across essentially the entire supported Windows codebase, consistent with a component maintained in the core OS rather than an add-on.
Know when Windows Server 2012 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
Local foothold with low privileges (AV:L/PR:L), race-condition timing makes it high-complexity (AC:H), and successful escalation yields full SYSTEM control (C:H/I:H/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
DescriptionCVE.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
Windows Telephony Service (TAPI) contains a privilege escalation flaw affecting Windows client and server systems (versions 10/11 and Server 2012-2025), allowing local attackers to achieve full system compromise. While no public exploit currently exists, the availability of a vendor patch indicates active remediation is required across the enterprise infrastructure to prevent insider threats and unauthorized privilege escalation.
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 Server 2012
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
Remote code execution in Microsoft Office 2007-2016 and Windows Vista through 10 allows attackers to execute arbitrary c
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
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
Active Directory Domain Services Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.5), this vulnerabilit
EUVD-2026-44126
GHSA-fx47-xcfr-9fc8
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB