Skip to main content

Sensor Data Service CVE-2026-83639

| EUVDEUVD-2026-99931 HIGH
Heap-based Buffer Overflow (CWE-122)
2026-10-13 secure@microsoft.com GHSA-782v-3m9c-g43p
7.8
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
    Send crafted input to Sensor Data Service
  3. Exploit
    Trigger heap buffer overflow (CWE-122)
  4. Execution
    Corrupt heap and hijack service execution
  5. Impact
    Elevate to SYSTEM privileges

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

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 authenticated, low-privileged code execution on the target Windows host (CVSS PR:L, AV:L) and the ability to deliver crafted input to the local Windows Sensor Data Service to trigger the heap overflow. No remote vector exists and no user interaction is needed (UI:N). Limiting factors: the attacker must first obtain a local foothold, so this is a post-compromise escalation rather than an initial-access flaw, and only hosts running supported, unpatched Windows builds within the listed version ranges (e.g. Windows 11 24H2 <10.0.26100.9711, Windows Server 2025 <10.0.26100.33650) are affected; no special non-default configuration is noted as required.

Impact

This is a genuine but second-tier priority. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N) describes a local privilege-escalation flaw: the attacker must already have authenticated code execution on the host (PR:L) and cannot reach the Sensor Data Service remotely. Impact is high across confidentiality, integrity and availability (C:H/I:H/A:H), consistent with the SSVC 'Technical Impact: total' rating, reflecting that successful exploitation yields full SYSTEM-level compromise. However, the signals converge on lower real-world urgency: SSVC 'Exploitation: none' and 'Automatable: no' indicate no observed exploitation and no reliable mass-automation path, there is no CISA KEV listing, and no public exploit code was identified in the input. The signals are internally consistent - a high-impact but access-gated local EoP that is not currently being exploited. The primary value of this bug to an attacker is as a post-compromise escalation step rather than an initial-access vector, so it should be patched on the normal Patch Tuesday cadence and prioritized on multi-user or shared hosts, but it does not warrant emergency out-of-band response absent new exploitation evidence.

Exploit ScenarioDerived

An attacker who has already gained low-privileged, authenticated access to a Windows host (for example via phishing, a stolen credential, or a browser-delivered payload) sends crafted input to the Windows Sensor Data Service to trigger a heap-based buffer overflow (CWE-122), corrupting heap memory to hijack execution within the service and escalate to SYSTEM. No public proof-of-concept exploit was identified at time of analysis, and the local-only vector (AV:L) means this cannot be launched remotely without prior foothold.

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 14, 2026

Local privilege escalation in the Windows Sensor Data Service lets an authenticated, low-privileged attacker who already holds code execution on a host corrupt the service's heap and run code in its higher-integrity context. The defect is a heap-based buffer overflow (CWE-122) tracked at CVSS 7.8 with the vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, making it a post-compromise escalation step rather than a remote or initial-access vector. No public exploit code and no confirmed active exploitation were identified at time of analysis, and Microsoft has published fixes covering the affected build ranges.

RemediationAI

Vendor-released patch: Microsoft has published updates through the MSRC Security Update Guide, and remediation is to apply the current cumulative update so each host meets or exceeds the patched build threshold for its release, i.e. 10.0.14393.9612 (Windows 10 1607 / Server 2016), 10.0.17763.9376 (Windows 10 1809 / Server 2019), 10.0.19044.7807 (Windows 10 21H2/22H2), 10.0.20348.5761 (Server 2022), 10.0.22631.7652 (Windows 11 23H2), 10.0.26100.33650 (Server 2025), 10.0.26100.9711 (Windows 11 24H2), 10.0.26200.9711 (Windows 11 25H2), 10.0.26300.9711 (Windows 11 26H2) and 10.0.28000.3231 (Windows 11 26H1); confirm the installed build with a standard OS build query before and after deployment, since the same 10.0.26100 base is used by both Windows 11 24H2 and Server 2025 with different thresholds. Because exploitation requires an existing authenticated local foothold (AV:L/PR:L), the highest-value compensating control is shrinking that foothold: restrict interactive/RDP logon and local code execution to trusted accounts, enforce application control such as WDAC or AppLocker to block untrusted binaries, and remove unnecessary local administrator rights and service-account privileges; the trade-off is operational friction for developers and administrators who legitimately run custom code on endpoints. Where the sensor feature set is not business-required, disabling the Sensor Data Service (setting SensorDataService/SensorService to Disabled and stopping it) eliminates the vulnerable IPC surface entirely, but it breaks sensor-dependent functionality such as auto-rotation, adaptive brightness and sensor-aware applications, and it is not a substitute for patching. For detection in the interim, monitor EDR telemetry for anomalous child processes, heap-corruption crashes or unexpected writes originating from the sensor service process, and alert on unusual local IPC traffic to it; blocking network access is not a meaningful control here because the vector is strictly local. Prioritize hosts where low-privileged users routinely execute code, and treat this as a post-compromise hardening item rather than an initial-access emergency.

Affected VersionsENISA

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

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_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 16 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 Sensor Data Service (SensorDataService, exposed through the sensor platform that feeds accelerometer, ambient-light, gyroscope and similar data to WinRT and desktop consumers) runs as a privileged system service and accepts locally supplied input over its IPC surface. The root cause is CWE-122, a heap-based buffer overflow: a length or size value derived from attacker-influenced input is not validated before a heap allocation is written, so an out-of-bounds write can overwrite adjacent heap metadata and objects. Because the write occurs in a service context, successful corruption can be shaped into arbitrary code execution at that service's privilege level, which is why the assessed impact is total (C:H/I:H/A:H) with scope unchanged (S:U). The assessed vector AV:L/AC:L/PR:L/UI:N confirms this is reachable only by a local, authenticated principal, requires no user interaction, and has low attack complexity once a foothold exists; there is no network-reachable path and no noted non-default configuration prerequisite. CPE-derived affected families span the modern Windows kernel base builds (10.0.14393, 10.0.17763, 10.0.19044/19045, 10.0.20348, 10.0.22631, 10.0.26100, 10.0.26200, 10.0.26300, 10.0.28000), covering both client and Server Core installations.

Know when the next one hits your stack

  • 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.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local service exploited by an existing low-privileged user (AV:L/PR:L), no user interaction, reliably triggerable (AC:L), yielding full SYSTEM compromise (C:H/I:H/A:H).

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 VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
Low
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.8

DescriptionCVE.org

Heap-based buffer overflow in Windows Sensor Data Service allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

Microsoft Windows Sensor Data Service contains a local privilege escalation vulnerability (CVE-2026-83639) that allows an authenticated attacker with existing low-privileged code execution to gain higher-integrity access on the host. Organizations running affected Windows builds face increased risk of lateral movement, data exfiltration, or ransomware deployment if an attacker already has a foothold. Leadership should prioritize patching because this flaw turns a limited compromise into full system control.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Ubiquitous
core Windows OS component across all supported client and server builds
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
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

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

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