Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate locally with low privileges
  2. Delivery
    Invoke Windows Telephony Server operation
  3. Exploit
    Trigger use-after-free race condition
  4. Execution
    Reclaim freed object with controlled data
  5. Impact
    Elevate privileges to SYSTEM

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires the attacker to already have authenticated, low-privileged local access to the target host (CVSS PR:L, AV:L) - this is a privilege-escalation primitive, not a remote entry point. The high attack complexity (AC:H) reflects a use-after-free race condition that must be reliably won, making exploitation timing-dependent and less deterministic. No user interaction is required (UI:N). The Windows Telephony Server service must be present and reachable by the attacker's process; it ships enabled across supported Windows editions, so no non-default configuration is needed. Primary limiting factors: the need for a pre-existing local account and the difficulty of winning the race reliably, which together constrain this to post-compromise escalation scenarios, especially relevant on multi-user and session-host systems.

Impact

This is a moderate-priority, not emergency, patch. The CVSS 3.1 base score is 7.0 (High) with vector AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, meaning exploitation requires local access, already-held low privileges, AND a high-complexity precondition (AC:H) - consistent with a use-after-free (CWE-416) race condition that an attacker must win reliably. The SSVC decision framework reinforces this downgrade: Exploitation is rated 'none' (no observed or public exploitation), Automatable is 'no' (AC:H race conditions cannot be reliably mass-automated), while Technical Impact is 'total' (full SYSTEM-level compromise if successful). No CISA KEV listing and no POC are present in the provided data, and there is no EPSS score supplied to gauge exploitation probability - its absence is a data gap, not a signal. The signals are internally consistent: high technical impact but constrained, non-automatable, local-only exploitation with no evidence of in-the-wild use. This is a classic 'high CVSS, contained real-world risk' local privilege-escalation that belongs in the standard Patch Tuesday cycle rather than emergency out-of-band remediation, prioritized on multi-user hosts, RDP/session hosts, and shared workstations where low-privileged attackers are present.

Exploit ScenarioDerived

A low-privileged but authenticated local user (e.g., on a shared terminal server or a workstation where the attacker already has a foothold) executes code that interacts with the Windows Telephony Server service to trigger a use-after-free condition. By winning a timing-dependent race to reclaim the freed object with attacker-controlled data, they corrupt memory to execute code in the service's security context and elevate to SYSTEM. No public exploit identified at time of analysis, and the AC:H rating means the race must be won reliably, reducing real-world ease of exploitation.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

A use-after-free (CWE-416) in the Windows Telephony Server (TapiSrv) component lets an authenticated, low-privileged local attacker escalate to higher privileges on affected Windows hosts. Exploitation requires a pre-existing local account plus a winning a timing-sensitive memory-reuse race (CVSS 3.1 AV:L/AC:H/PR:L/UI:N), so this is a post-compromise escalation primitive rather than a remote entry point; no public exploit code and no confirmed active exploitation were identified at time of analysis (CISA SSVC: Exploitation = none), and CISA SSVC rates technical impact as total, but the local-access and race-condition prerequisites keep this a moderate-priority patch rather than an emergency one. Microsoft has released fixes for the affected builds, so priority should be normal-cycle patching, with elevated urgency on multi-user and session-host systems where low-privileged accounts are common.

RemediationAI

Apply the vendor-released Microsoft security update for CVE-2026-85810 via the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85810); the patch brings systems to or above the fixed builds Windows 10 1607 / Server 2016 10.0.14393.9612, Windows 10 1809 / Server 2019 10.0.17763.9376, Windows 10 21H2 and 22H2 10.0.19044.7807, Windows 11 23H2 10.0.22631.7652, Windows 11 24H2 10.0.26100.9711, Windows 11 25H2 10.0.26200.9711, Windows 11 26H2 10.0.26300.9711, Windows 11 26H1 10.0.28000.3231, Server 2022 10.0.20348.5761, Server 2025 10.0.26100.33650, Server 2012 6.2.9200.26434, and Server 2012 R2 6.3.9600.23470. As a compensating control on systems that cannot be patched immediately, restrict interactive local logons and multi-user/RDP access so that untrusted low-privileged accounts cannot reach the service - this preserves the service but only reduces exposure where account control is strict. Stopping or disabling the Telephony (TapiSrv) service does close the attack surface, but the trade-off is significant: TAPI-dependent functionality such as dial-up/VPN and RRAS remote access, modem, fax, and unified-messaging integrations will stop working, so treat that as a short-term containment measure on isolated or high-value session hosts only. Because the vulnerability is a timing-dependent local race rather than a remote primitive, perimeter controls and network filtering are not effective mitigations; prioritize patching on multi-user, RDP/session-host, and terminal-server style systems where low-privileged local accounts are most likely to exist.

Affected VersionsENISA

Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26434
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows Server 2012 6.2.9200.0 <6.2.9200.26434
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2012 fix: 6.2.9200.26434
euvd windows_server_2012_r2 fix: 6.3.9600.23470
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23470
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26434
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 20 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 vulnerability is a use-after-free (CWE-416) in the Windows Telephony Server service (TapiSrv), the service that brokers TAPI (Telephony API) requests for telephony, modem, fax, and remote-access/dial-up functionality on Windows. Use-after-free means a heap object is freed while a reference to it remains live; a local attacker who can drive concurrent operations into the service can cause that dangling reference to be reused, corrupting memory in the service's process context. Because the service runs with elevated (SYSTEM-level) privileges, controlled corruption inside it converts an authenticated low-privileged session into code execution at the service's privilege level. The assessed vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H reflects the exact prerequisites: local access (AV:L), a low-privileged authenticated account (PR:L), no user interaction (UI:N), and high attack complexity (AC:H) because the race window must be won reliably - exploitation is timing-dependent and not fully deterministic, and carries impact to confidentiality, integrity, and availability within the same security scope. The service is present and enabled by default across supported Windows client and server editions, so no non-default configuration is required; the primary constraints are the need for an existing local foothold and the difficulty of a stable race.

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

Vendor (microsoft) PRIMARY 7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Local-only use-after-free (AV:L) exploitable by an already-authenticated low-privileged user (PR:L) via a hard-to-win race condition (AC:H), yielding full SYSTEM compromise (C:H/I:H/A:H).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:21 cve.org
HIGH 7.0

DescriptionCVE.org

Use after free in Windows Telephony Server allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A privilege-escalation flaw in the Windows Telephony Server (TapiSrv) component shipped with supported Windows builds allows an attacker who already holds a low-privileged local account to gain higher rights on the same machine. Because exploitation demands both an existing foothold on the host and a hard-to-win timing condition, the practical risk is a post-compromise escalation step rather than a new way into the environment, but the resulting access is total on any system where it succeeds. Leadership should care most about shared, multi-user and session-host systems (VDI, RDS/Citrix, jump hosts, developer workstations), where low-privileged accounts are abundant and one successful escalation can expose other users' sessions and data; Microsoft has released fixes, so this is a normal-cycle patch with heightened urgency on those systems rather than an emergency.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 85% exploitable
Prevalence
Ubiquitous
Telephony Server component ships across all supported Windows client and server editions
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy