CyberSecBulletin
CVE-2026-105575NVD status: Undergoing Analysis

Windows 10 Version 1809: Access of Resource Using Incompatible Type

CVE-2026-105575 is a high-severity access of resource using incompatible type vulnerability in Windows 10 Version 1809 from Microsoft, with a CVSS 3.1 base score of 7.8 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.17763.9487 as the first without the flaw, so updating Windows 10 Version 1809 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 1809 to 10.0.17763.9487 or a later version.
  2. Update Windows 10 Version 21H2 to 10.0.19044.7846 or a later version.
  3. Update Windows 10 Version 22H2 to 10.0.19045.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 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 26H210.0.26300.0 up to, but not including, 10.0.26300.997410.0.26300.9974
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
LowNo special conditions are needed; the attack works reliably.
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:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).

Official description

Access of resource using incompatible type ('type confusion') in Windows DWM Core Library 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: Access of Resource Using Incompatible Type

The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.

More Access of Resource Using Incompatible Type vulnerabilities (CWE-843)

Timeline

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

References

Recent Access of Resource Using Incompatible Type vulnerabilities

Spotted an error? Tell us.