Actively exploitedKnown ransomware use

CVE-2025-26633 Microsoft Windows Management Console (MMC) Improper Neutralization Vulnerability

Microsoft Windows Management Console (MMC) contains an improper neutralization vulnerability that allows an unauthorized attacker to bypass a security feature locally.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 11 Mar 2025.
  • CISA lists it as known to be used in ransomware campaigns.
  • Rated High severity (CVSS 7.0, scored by Vendor).
  • It has been in the catalogue for 605 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

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

Affected Versions

ProductVersions
Microsoft Windows 10 Version 150710.0.10240.0 to before 10.0.10240.20947
Microsoft Windows 10 Version 160710.0.14393.0 to before 10.0.14393.7876
Microsoft Windows 10 Version 180910.0.17763.0 to before 10.0.17763.7009
Microsoft Windows 10 Version 21H210.0.19044.0 to before 10.0.19044.5608
Microsoft Windows 10 Version 22H210.0.19045.0 to before 10.0.19045.5608
Microsoft Windows 11 version 22H210.0.22621.0 to before 10.0.22621.5039

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Microsoft Windows. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2025-26633 and every other exploited flaw on the list.

Check My Exposure