CyberSecBulletin
CVE-2026-96066NVD status: Undergoing Analysis

Windows 10 Version 1809: Stack-based Buffer Overflow

Published Updated By the CyberSecBulletin desk

CVE-2026-96066 is a high-severity stack-based buffer overflow 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.31% 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 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 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

Stack-based buffer overflow in Windows Local Security Authority Subsystem Service (LSASS) 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: Stack-based Buffer Overflow

The product writes past the end of a buffer that was allocated on the stack.

How developers prevent this class of flaw

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
  • Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Implement and perform bounds checking on input.

More Stack-based Buffer Overflow vulnerabilities (CWE-121)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Stack-based Buffer Overflow vulnerabilities

Spotted an error? Tell us.