Skip to main content

Windows Phone Service CVE-2026-85357

| EUVDEUVD-2026-99483 HIGH
Race Condition (CWE-362)
2026-10-13 secure@microsoft.com GHSA-437j-h7r2-qjpx
7.0
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privileged local foothold
  2. Delivery
    Launch process targeting Windows Phone Service
  3. Exploit
    Race shared resource synchronization window
  4. Execution
    Win timing to corrupt state
  5. Impact
    Elevate 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 possess a local, low-privileged authenticated account (PR:L) on an affected build of Windows 11 (23H2 through 26H2) or Windows Server 2022 - this is not remotely reachable (AV:L). The core limiting factor is the race-condition timing: per CVSS AC:H, the attacker must repeatedly and reliably win a narrow synchronization window in the Windows Phone Service shared resource, which is non-deterministic and typically requires many attempts. No user interaction is needed (UI:N), and the flaw affects default configurations of the vulnerable component, but the combination of required local access plus difficult timing substantially narrows realistic exploitation.

Impact

This is a genuine but non-urgent patch-cycle item rather than an emergency. The CVSS 3.1 base score of 7.0 (High) is driven by total impact (C:H/I:H/A:H) tempered by significant barriers: the vector is local-only (AV:L), requires high attack complexity (AC:H - characteristic of race conditions that need precise timing to win), and already needs a foothold with low privileges (PR:L). All exploitation signals point AWAY from imminent mass exploitation: CISA SSVC lists Exploitation as 'none' and Automatable as 'no', there is no CISA KEV listing, and no public exploit was identified in the provided data. The only amplifying factor is SSVC Technical Impact 'total', which is consistent with a privilege-escalation outcome. In short, high technical impact is offset by low real-world exploitation likelihood and difficult exploitation conditions - this should be prioritized within normal Patch Tuesday remediation, not treated as a drop-everything zero-day. One data inconsistency to note: the input Tags include 'Information Disclosure', yet both the description and the CVSS impact profile describe a local elevation-of-privilege race condition, so that tag appears mislabeled.

Exploit ScenarioDerived

An attacker who already has a low-privileged local account on an affected Windows 11 or Windows Server 2022 host runs a program that repeatedly triggers the Windows Phone Service while racing a shared resource. By winning the timing window (which takes many attempts given the high attack complexity), the attacker corrupts synchronization state and gains SYSTEM-level privileges. No public exploit code was identified at time of analysis, and no user interaction is required.

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

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

Alert me

AnalysisAIv1 – Oct 14, 2026

Local privilege escalation in the Windows Phone Service on Windows 11 (23H2 through 26H2) and Windows Server 2022 lets an authenticated, low-privileged user on the machine win a race condition in a shared resource and elevate to a higher-integrity context, with high impact to confidentiality, integrity, and availability (CVSS 7.0, AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack is not remotely reachable and requires a pre-existing local account, and the AC:H rating reflects that a narrow, non-deterministic synchronization window must be won reliably - typically over many repeated attempts - so this is a patch-cycle item rather than an emergency. No public exploit code and no confirmed active exploitation were identified at time of analysis (CISA SSVC: Exploitation none, Automatable no). Vendor patches are available per the MSRC advisory.

RemediationAI

Vendor-released patch: apply the Microsoft security update for CVE-2026-85357, which brings affected systems to the fixed builds Windows 11 23H2 10.0.22631.7652, 24H2 10.0.26100.9711, 25H2 10.0.26200.9711, 26H1 10.0.28000.3231, 26H2 10.0.26300.9711, and Windows Server 2022 10.0.20348.5761; the update and per-build guidance are published at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85357. Standard Windows Update / WSUS / Microsoft Update Catalog delivery applies, and the fix requires a reboot. Because exploitation requires a pre-existing low-privileged local account, the most effective compensating control while patching is reducing the local attack surface: audit and remove unnecessary local accounts and guest/elevated local groups, and restrict interactive logon and Remote Desktop rights to users who genuinely need them (trade-off: may disrupt shared-workstation or lab/demo usage, especially on phone-enabled or telephony-integrated endpoints). If the affected service is not required on a given host, disabling the associated telephony/phone service startup rather than leaving it running reduces exposure (trade-off: it can break telephony, calling, and linked-app functionality). Because the exploit is timing-based and non-automatable, add detection around repeated rapid process attempts against the phone service and around unexpected token or integrity-level changes by non-administrative accounts rather than relying on signature-based prevention. There is no metered per-request mitigation to apply and no evidence of exploitation to drive emergency out-of-band deployment.

Affected VersionsENISA

Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows Server 2022 10.0.20348.0 <10.0.20348.5761

Affected Packages

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_2022 fix: 10.0.20348.5761

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 6 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 root cause is CWE-362, concurrent execution using a shared resource with improper synchronization, i.e. a race condition inside the Windows Phone Service component shipped with Windows 11 and Windows Server 2022. Concurrent operations against the service's shared state (a handle, object, or cached resource) can be interleaved so that the attacker's low-privileged process observes or manipulates the resource after a security check but before the privileged operation completes - the classic time-of-check/time-of-use window. Per the authoritative assessment, this is purely a local attack path (AV:L): the attacker must already hold a low-privileged authenticated account on the affected build (PR:L), and no user interaction is required (UI:N). The high attack complexity (AC:H) quantifies the difficulty of hitting the synchronization window deterministically, and scope is unchanged (S:U), meaning the privilege gained stays within the existing Windows security authority. CISA SSVC judges the flaw non-automatable and technical impact total, consistent with the C:H/I:H/A:H vector, but not currently exploited. CPE data identifies the exposed platforms as Windows 11 builds 10.0.22631, 10.0.26100, 10.0.26200, 10.0.26300, and 10.0.28000, plus Windows Server 2022 build 10.0.20348.

Know when Windows 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 privilege escalation requiring an existing low-priv account (PR:L, AV:L) and winning a timing-sensitive race (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:20 cve.org
HIGH 7.0

DescriptionCVE.org

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Phone Service allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A local privilege-escalation flaw in the Windows Phone Service affects Windows 11 builds 23H2 through 26H2 and Windows Server 2022, letting a user who already holds a low-privileged local account seize higher-integrity privileges on the host and gain broad control over its data, services, and availability. Exploitation requires that pre-existing local account and a narrow timing race that must be won reliably over repeated attempts, and with no public exploit identified at time of analysis this is a scheduled patch-cycle item rather than an emergency for most organizations. Leadership should care most where many users share one host - VDI pools, Remote Desktop Session Hosts, jump boxes, and Windows Server 2022 systems - because a single compromised account there could be escalated into full control of a shared system.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Ubiquitous
Affects mainstream Windows 11 and Windows Server 2022 across all environments
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
4 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.2%
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

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).

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2025-13315 CRITICAL POC
9.3 Nov 19

Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-13316 HIGH POC
8.2 Nov 19

Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

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