High7.0Microsoft Server Exploited CISA KEV

High [CVE-2025-26633] Microsoft Management Console Security Feature Bypass Vulnerability

This high-severity Microsoft Server advisory covers CVE-2025-26633 affecting Windows Server 2008 R2 Service Pack 1 (Server Core installation), Windows Server 2008 Service Pack 2 (Server Core installation), Windows Server 2012 (Server Core installation).

CVE-2025-26633 Published Mar 11, 2025Updated by vendor Aug 5, 2026

CVE-2025-26633

Affected products & platforms

Microsoft ServerWindows Server

Open vendor advisory

Android app · Google Play

Monitor future Microsoft Server CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Get CVE alerts See app features

Summary

Improper neutralization in Microsoft Management Console allows an unauthorized attacker to bypass a security feature locally.

Affected products named by the advisory: Windows Server 2008 R2 Service Pack 1; Windows Server 2008 R2 Service Pack 1 (Server Core installation); Windows Server 2008 Service Pack 2; Windows Server 2008 Service Pack 2 (Server Core installation); and 12 more.

Affected products named by the advisory: Windows Server 2012 (Server Core installation); Windows Server 2012 R2 (Server Core installation); Windows Server 2016 (Server Core installation); Windows Server 2019 (Server Core installation); and 2 more.

CISA Known Exploited Vulnerability

Listed:: Mar 11, 2025 · federal remediation due Apr 1, 2025
Required action:: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Ransomware use:: Known

KEV is a prioritization signal from CISA — remediation detail still comes from the vendor advisory.

Affected versions

Windows 10 Version 1507 10.0.10240.0 before 10.0.10240.20947
Windows 10 Version 1607 10.0.14393.0 before 10.0.14393.7876
Windows 10 Version 1809 10.0.17763.0 before 10.0.17763.7009
Windows 10 Version 21H2 10.0.19044.0 before 10.0.19044.5608
Windows 10 Version 22H2 10.0.19045.0 before 10.0.19045.5608
Windows 11 version 22H2 10.0.22621.0 before 10.0.22621.5039
Windows 11 version 22H3 10.0.22631.0 before 10.0.22631.5039
Windows 11 Version 23H2 10.0.22631.0 before 10.0.22631.5039
Windows 11 Version 24H2 10.0.26100.0 before 10.0.26100.3476
Windows Server 2008 R2 Service Pack 1 6.1.7601.0 before 6.1.7601.27618
Windows Server 2008 R2 Service Pack 1 (Server Core installation) 6.1.7601.0 before 6.1.7601.27618
Windows Server 2008 Service Pack 2 6.0.6003.0 before 6.0.6003.23168

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Fixed versions

10.0.10240.20947
10.0.14393.7876
10.0.17763.7009
10.0.19044.5608
10.0.19045.5608
10.0.22621.5039
10.0.22631.5039
10.0.26100.3476
6.1.7601.27618
6.0.6003.23168
6.2.9200.25368
6.3.9600.22470

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Mitigation

Upgrade to a fixed release: 10.0.10240.20947, 10.0.14393.7876, 10.0.17763.7009, 10.0.19044.5608, 10.0.19045.5608, 10.0.22621.5039. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.