Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Authenticate with low-privilege local account
  2. Delivery
    Invoke vulnerable Windows Speech code path
  3. Exploit
    Trigger use-after-free and reclaim freed object
  4. Execution
    Corrupt memory to hijack execution
  5. Impact
    Elevate to SYSTEM privileges

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

Exploitation requires the attacker to already possess valid low-level local privileges (PR:L) and interactive/local access to the target host (AV:L); it cannot be performed remotely or unauthenticated. No user interaction is needed (UI:N) and attack complexity is low (AC:L), meaning once a local foothold exists the trigger is reliable. The limiting factors are the need for an existing authenticated account with local logon capability and code execution on the machine, which is why CISA SSVC rates the flaw non-automatable; systems where untrusted users can log in locally (shared workstations, RDS/terminal/Citrix servers, jump boxes) face the highest realistic risk, while single-user, well-restricted endpoints are lower priority.

Impact

The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) describes a local, low-complexity, low-privilege escalation with high confidentiality, integrity, and availability impact - consistent with an authenticated user gaining full control of the host. Multiple secondary signals moderate the urgency: CISA SSVC records Exploitation as 'none' and Automatable as 'no' while confirming Technical Impact as 'total', and EPSS is low at 0.26% (18th percentile). These agree with the local attack vector: this is a valuable post-compromise privilege-escalation primitive rather than a remotely wormable threat, so it is not automatable and unlikely to see mass, opportunistic exploitation. It remains a real priority for patch prioritization on multi-user and server systems because the impact is total and a fix is already available, but it ranks below any internet-facing RCE. No conflict exists between the signals - the local vector, non-automatable SSVC, and low EPSS are mutually consistent.

Exploit ScenarioDerived

An attacker who already has a low-privileged authenticated foothold on a Windows host - for example a standard domain user on a shared terminal server or a limited account obtained through phishing - invokes the vulnerable Windows Speech code path and triggers the use-after-free, grooming the freed memory to hijack execution. Successful exploitation elevates the attacker to SYSTEM, giving full control of the machine. No public exploit code is identified at this time, and exploitation requires local access with low but valid privileges.

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

AnalysisAIv2 – Jul 16, 2026

Local privilege escalation in the Windows Speech component affects a broad range of Windows client and server releases (Windows 10 1607 through Windows 11 26H1, and Windows Server 2016 through 2025). A use-after-free flaw (CWE-416) lets an authenticated local attacker corrupt memory to gain SYSTEM-level privileges; CVSS is 7.8 with total technical impact per CISA SSVC. There is no public exploit identified at time of analysis, and EPSS is low at 0.26%, but a vendor patch is available via Microsoft's MSRC update guide.

Earlier versions of this analysis (1)
v1 Jul 14, 2026 - 17:42 CVSS 7.5

Local privilege elevation in the Windows Speech component (Text-to-Speech / speech runtime) affects a broad range of Windows 10, Windows 11, and Windows Server releases, where a use-after-free (CWE-416) lets an already-authenticated local user corrupt memory to run code at higher privilege. Exploitation is non-trivial - it requires local access, low-level authentication, user interaction, and winning a memory-timing condition - and the CVSS 7.5 rating reflects a scope-changed, high-impact outcome. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV, so this is a patch-on-cycle EoP rather than an emergency.

RemediationAI

Vendor-released patch: apply the Microsoft cumulative update that brings each system to at least its fixed build - 10.0.14393.9339 (1607/Server 2016), 10.0.17763.9020 (1809/Server 2019), 10.0.19044.7548 (21H2), 10.0.19045.7548 (22H2), 10.0.20348.5386 (Server 2022), 10.0.26100.8875 (Windows 11 24H2/25H2), 10.0.26100.33158 (Server 2025), and 10.0.28000.2269 (26H1) - per the advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-49171. Patching through Windows Update or WSUS is the definitive fix and should be prioritized on shared workstations, RDS/terminal servers, and any multi-user hosts where untrusted users hold local logon rights. If patching must be deferred, reduce exposure by restricting interactive and remote-desktop logon rights to trusted accounts (this only limits, not eliminates, the local attacker prerequisite) and, where Speech features are not needed, minimizing use of speech recognition/text-to-speech functionality - noting that no official standalone workaround is published by Microsoft, so the update remains the only reliable mitigation.

Affected VersionsENISA

Windows Server 2016 10.0.14393.0 <10.0.14393.9339
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7548
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33158
Windows Server 2025 10.0.26100.0 <10.0.26100.33158
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9020
Windows Server 2022 10.0.20348.0 <10.0.20348.5386
Windows Server 2019 10.0.17763.0 <10.0.17763.9020
Windows 11 Version 25H2 10.0.26200.0 <10.0.26100.8875
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9339
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7548
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9339
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8875
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9020

Affected Packages

microsoft windows_10_version_1607_10_0_14393_9339 fix: Windows 10 Version 1607 for 32-bit Systems 10.0.14393.9339, Windows 10 Version 1607 for x64-based Systems 10.0.14393.9339
microsoft windows_10_version_1809_10_0_17763_9020 fix: Windows 10 Version 1809 for 32-bit Systems 10.0.17763.9020, Windows 10 Version 1809 for x64-based Systems 10.0.17763.9020
microsoft windows_10_version_21h2_10_0_19044_7548 fix: Windows 10 Version 21H2 for 32-bit Systems 10.0.19044.7548, Windows 10 Version 21H2 for ARM64-based Systems 10.0.19044.7548, Windows 10 Version 21H2 for x64-based Systems 10.0.19044.7548
microsoft windows_10_version_22h2_10_0_19045_7548 fix: Windows 10 Version 22H2 for 32-bit Systems 10.0.19045.7548, Windows 10 Version 22H2 for ARM64-based Systems 10.0.19045.7548, Windows 10 Version 22H2 for x64-based Systems 10.0.19045.7548
microsoft windows_11_version_24h2_10_0_26100_8875 fix: Windows 11 Version 24H2 for ARM64-based Systems 10.0.26100.8875, Windows 11 Version 24H2 for x64-based Systems 10.0.26100.8875
microsoft windows_11_version_25h2_10_0_26100_8875 fix: Windows 11 Version 25H2 for ARM64-based Systems 10.0.26100.8875, Windows 11 Version 25H2 for x64-based Systems 10.0.26100.8875
microsoft windows_11_version_26h1_10_0_28000_2269 fix: Windows 11 version 26H1 for x64-based Systems 10.0.28000.2269
microsoft windows_11_version_26h1_10_0_28000_2525 fix: Windows 11 Version 26H1 for ARM64-based Systems 10.0.28000.2525
microsoft windows_server_2016_10_0_14393_9339 fix: Windows Server 2016 10.0.14393.9339, Windows Server 2016 (Server Core installation) 10.0.14393.9339
microsoft windows_server_2019_10_0_17763_9020 fix: Windows Server 2019 10.0.17763.9020, Windows Server 2019 (Server Core installation) 10.0.17763.9020
microsoft windows_server_2022_10_0_20348_5386 fix: Windows Server 2022 10.0.20348.5386
microsoft windows_server_2025_10_0_26100_33158 fix: Windows Server 2025 10.0.26100.33158, Windows Server 2025 (Server Core installation) 10.0.26100.33158
euvd windows_10_version_1607 fix: 10.0.14393.9339
euvd windows_10_version_1809 fix: 10.0.17763.9020
euvd windows_10_version_21h2 fix: 10.0.19044.7548
euvd windows_10_version_22h2 fix: 10.0.19045.7548
euvd windows_11_version_24h2 fix: 10.0.26100.8875
euvd windows_11_version_25h2 fix: 10.0.26100.8875
euvd windows_11_version_26h1 fix: 10.0.28000.2269
euvd windows_server_2016 fix: 10.0.14393.9339
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9339
euvd windows_server_2019 fix: 10.0.17763.9020
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9020
euvd windows_server_2022 fix: 10.0.20348.5386
euvd windows_server_2025 fix: 10.0.26100.33158
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33158

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 26 packages in microsoft, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in Windows Speech, the speech recognition and text-to-speech subsystem built into Windows, which runs with access to local user context and system resources. The root cause is CWE-416 (Use After Free): the component continues to reference a memory object after it has been freed, allowing an attacker to reoccupy that freed allocation with attacker-controlled data and manipulate program flow when the dangling pointer is dereferenced. The CPE data confirms this is a first-party Microsoft flaw spanning both client (Windows 10 1607/1809/21H2/22H2, Windows 11 24H2/25H2/26H1) and server SKUs (Server 2016/2019/2022/2025, including Server Core installations), indicating the vulnerable Speech code is shared across the modern Windows codebase rather than isolated to a single edition.

Know when Windows Server 2016 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 HIGH
NVD 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CIRCL (temporal) 6.5 MEDIUM
vuln.today AI 7.8 HIGH

Local vector and low existing privileges are required (AV:L/PR:L), no user interaction, and a use-after-free yielding SYSTEM gives high C/I/A within an unchanged scope.

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

Primary rating from Vendor (microsoft).

CVSS VectorNVD

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

Lifecycle Timeline

3
Analysis Updated
Jul 16, 2026 - 16:13 vuln.today
v2 - CVSS changed
CVSS changed
Jul 16, 2026 - 16:07 NVD
7.5 (HIGH) 7.8 (HIGH)
CVE Published
Jul 14, 2026 - 17:04 nvd
HIGH 7.5

DescriptionNVD

Use after free in Microsoft Windows Speech allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A use-after-free vulnerability in Windows Speech (CVE-2026-49171, CVSS 7.8) enables any authenticated local user to escalate to SYSTEM privileges, creating a persistent backdoor for data theft and lateral movement. The flaw affects Windows 10, 11, and Server 2016-2025-covering the vast majority of enterprise Windows infrastructure-making this a broad organizational exposure. Microsoft has released a patch; rapid deployment is essential to prevent post-breach privilege escalation attacks.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 82% exploitable
Prevalence
Ubiquitous
Microsoft Windows client and server, deployed across most enterprise environments
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
6 sources
Confidence: High

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
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
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