CyberSecBulletin
CVE-2026-119822NVD status: Awaiting Analysis

Windows 10 Version 1607: Exposure of Sensitive System Information to an Unauthorized Control Sphere

CVE-2026-119822 is a high-severity exposure of sensitive system information to an unauthorized control sphere vulnerability in Windows 10 Version 1607 from Microsoft, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 10.0.14393.9688 as the first without the flaw, so updating Windows 10 Version 1607 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.36% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Windows 10 Version 1607 to 10.0.14393.9688 or a later version.
  2. Update Windows 10 Version 1809 to 10.0.17763.9487 or a later version.
  3. Update Windows 10 Version 21H2 to 10.0.19044.7846 or a later version.
  4. Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 160710.0.14393.0 up to, but not including, 10.0.14393.968810.0.14393.9688
MicrosoftWindows 10 Version 180910.0.17763.0 up to, but not including, 10.0.17763.948710.0.17763.9487
MicrosoftWindows 10 Version 21H210.0.19044.0 up to, but not including, 10.0.19044.784610.0.19044.7846
MicrosoftWindows 10 Version 22H210.0.19045.0 up to, but not including, 10.0.19045.784610.0.19045.7846
MicrosoftWindows 11 version 23H210.0.22631.0 up to, but not including, 10.0.22631.771110.0.22631.7711
MicrosoftWindows 11 Version 24H210.0.26100.0 up to, but not including, 10.0.26100.997410.0.26100.9974
MicrosoftWindows 11 Version 25H210.0.26200.0 up to, but not including, 10.0.26200.997410.0.26200.9974
MicrosoftWindows 11 version 26H110.0.28000.0 up to, but not including, 10.0.28000.350110.0.28000.3501
MicrosoftWindows 11 Version 26H210.0.26300.0 up to, but not including, 10.0.26300.997410.0.26300.9974
MicrosoftWindows Server 201610.0.14393.0 up to, but not including, 10.0.14393.968810.0.14393.9688
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0 up to, but not including, 10.0.14393.968810.0.14393.9688
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.948710.0.17763.9487
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.948710.0.17763.9487
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.587010.0.20348.5870
MicrosoftWindows Server 202510.0.26100.0 up to, but not including, 10.0.26100.3382210.0.26100.33822
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0 up to, but not including, 10.0.26100.3382210.0.26100.33822

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).

Official description

Exposure of sensitive system information to an unauthorized control sphere in Windows Overlay Filter allows an authorized attacker to elevate privileges locally.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Exposure of Sensitive System Information to an Unauthorized Control Sphere

The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.

How developers prevent this class of flaw

  • Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user. All error message text should be HTML entity encoded before being written to the log file to protect against potential cross-site scripting attacks against the viewer of the logs

More Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerabilities (CWE-497)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).

References

Recent Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerabilities

Spotted an error? Tell us.