CVE-2026-65790: Windows Message Queuing Elevation of Privilege Vulnerability
Published Aug 11, 2026
·Updated
Heap-based buffer overflow in Windows Message Queuing allows an authorized attacker to elevate privileges locally.
Other sources
Windows Message Queuing Elevation of Privilege Vulnerability
— Microsoft
Affected Software
54 affected componentsFixes available
Microsoft Windows 10=22H2
10.0.19045.7663
Microsoft Windows 10=21H2
10.0.19044.7663
Microsoft Windows 10=21H2
10.0.19044.7663
Microsoft Windows 10=21H2
10.0.19044.7663
Microsoft Windows Server 2022<10.0.20348.5499, <10.0.20348.5440
10.0.20348.549910.0.20348.5440
Microsoft Windows Server 2022<10.0.20348.5499, <10.0.20348.5440
10.0.20348.549910.0.20348.5440
Microsoft Windows Server 2019<10.0.17763.9115
10.0.17763.9115
Microsoft Windows Server 2019<10.0.17763.9115
10.0.17763.9115
Microsoft Windows 10=22H2
10.0.19045.7663
Microsoft Windows 11=23H2
10.0.22631.7517
Microsoft Windows 10=1809
10.0.17763.9115
Microsoft Windows 10=1809
10.0.17763.9115
Microsoft Windows 11=23H2
10.0.22631.7517
Microsoft Windows 10=22H2
10.0.19045.7663
Microsoft Windows Server 2025<10.0.26100.33296, <10.0.26100.33222
10.0.26100.3329610.0.26100.33222
Microsoft Windows 10=1607
10.0.14393.9418
Microsoft Windows Server 2016<10.0.14393.9418
10.0.14393.9418
Microsoft Windows Server 2016<10.0.14393.9418
10.0.14393.9418
Microsoft Windows 10=1607
10.0.14393.9418
Microsoft Windows 11=26H1
10.0.28000.2704
Microsoft Windows 11=26H1
10.0.28000.2704
Microsoft Windows Server 2025<10.0.26100.33296, <10.0.26100.33222
10.0.26100.3329610.0.26100.33222
Microsoft Windows Server 2012 R2<6.3.9600.23338
6.3.9600.23338
Microsoft Windows Server 2012<6.2.9200.26280
6.2.9200.26280
Microsoft Windows Server 2012<6.2.9200.26280
6.2.9200.26280
Microsoft Windows Server 2012 R2<6.3.9600.23338
6.3.9600.23338
Microsoft Windows 11=25H2
10.0.26200.916810.0.26200.9106
Microsoft Windows 11=25H2
10.0.26200.916810.0.26200.9106
Microsoft Windows 11=24H2
10.0.26100.916810.0.26100.9106
Microsoft Windows 11=24H2
10.0.26100.916810.0.26200.9106
Microsoft Windows 10 1607<10.0.14393.9418
Microsoft Windows 10 1607<10.0.14393.9418
Microsoft Windows 10 1809<10.0.17763.9115
Microsoft Windows 10 1809<10.0.17763.9115
Microsoft Windows 10 21h2<10.0.19044.7663
Microsoft Windows 10 21h2<10.0.19044.7663
Microsoft Windows 10 21h2<10.0.19044.7663
Microsoft Windows 10 22h2<10.0.19045.7663
Microsoft Windows 10 22h2<10.0.19045.7663
Microsoft Windows 10 22h2<10.0.19045.7663
Microsoft Windows 11 23h2<10.0.22631.7517
Microsoft Windows 11 23h2<10.0.22631.7517
Microsoft Windows 11 24h2<10.0.26100.9106
Microsoft Windows 11 24h2<10.0.26100.9106
Microsoft Windows 11 25h2<10.0.26200.9106
Microsoft Windows 11 25h2<10.0.26200.9106
Microsoft Windows 11 26h1<10.0.28000.2704
Microsoft Windows 11 26h1<10.0.28000.2704
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.9418
Microsoft Windows Server 2019<10.0.17763.9115
Microsoft Windows Server 2022<10.0.20348.5440
Microsoft Windows Server 2025<10.0.26100.33222
Remediation
Event History
Aug 11, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
CVE Published
via MITRE·05:06 PM
Data Sourced
via MITRE·05:06 PM
DescriptionSeverity
Data Sourced
via NVD·05:18 PM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-65790?
The severity of CVE-2026-65790 is rated high with a score of 7.8.
2
How do I fix CVE-2026-65790?
You can fix CVE-2026-65790 by applying the available security patches from Microsoft.
3
What impact does CVE-2026-65790 have on systems?
CVE-2026-65790 allows an authorized attacker to elevate privileges locally on affected systems.
4
Which software versions are affected by CVE-2026-65790?
CVE-2026-65790 affects Microsoft Windows 10, Windows 11, various versions of Windows Server, and Windows 10 21h2.
5
Is there a workaround for CVE-2026-65790?
There are no specific workarounds for CVE-2026-65790, and applying the patch is the recommended solution.