CriticalCVE-2025-26633

    Microsoft Management Console Security Feature Bypass Vulnerability (CVE-2025-26633)

    Published Last modified In CISA KEV since Sources: pwn.watch, Msrc Update Guide, CVE.org

    What is affected, what to do

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

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. Update Microsoft Windows 10 Version 1507 to version 10.0.10240.20947, Microsoft Windows 10 Version 1607 to version 10.0.14393.7876, Microsoft Windows 10 Version 1809 to version 10.0.17763.7009. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Microsoft Windows 10 Version 1507 lt 10.0.10240.0..10.0.10240.20947
    • Microsoft Windows 10 Version 1607 lt 10.0.14393.0..10.0.14393.7876
    • Microsoft Windows 10 Version 1809 lt 10.0.17763.0..10.0.17763.7009
    • Microsoft Windows 10 Version 21H2 lt 10.0.19044.0..10.0.19044.5608
    • Microsoft Windows 10 Version 22H2 lt 10.0.19045.0..10.0.19045.5608
    • Microsoft Windows 11 version 22H2 lt 10.0.22621.0..10.0.22621.5039
    • Microsoft Windows 11 version 22H3 lt 10.0.22631.0..10.0.22631.5039
    • Microsoft Windows 11 Version 23H2 lt 10.0.22631.0..10.0.22631.5039
    • Microsoft Windows 11 Version 24H2 lt 10.0.26100.0..10.0.26100.3476
    • Microsoft Windows Server 2008 R2 Service Pack 1 lt 6.1.7601.0..6.1.7601.27618
    • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) lt 6.1.7601.0..6.1.7601.27618
    • Microsoft Windows Server 2008 Service Pack 2 lt 6.0.6003.0..6.0.6003.23168
    • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) lt 6.0.6003.0..6.0.6003.23168
    • Microsoft Windows Server 2012 lt 6.2.9200.0..6.2.9200.25368
    • Microsoft Windows Server 2012 (Server Core installation) lt 6.2.9200.0..6.2.9200.25368
    • Microsoft Windows Server 2012 R2 lt 6.3.9600.0..6.3.9600.22470
    • Microsoft Windows Server 2012 R2 (Server Core installation) lt 6.3.9600.0..6.3.9600.22470
    • Microsoft Windows Server 2016 lt 10.0.14393.0..10.0.14393.7876
    • Microsoft Windows Server 2016 (Server Core installation) lt 10.0.14393.0..10.0.14393.7876
    • Microsoft Windows Server 2019 lt 10.0.17763.0..10.0.17763.7009
    • Microsoft Windows Server 2019 (Server Core installation) lt 10.0.17763.0..10.0.17763.7009
    • Microsoft Windows Server 2022 lt 10.0.20348.0..10.0.20348.3328
    • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) lt 10.0.25398.0..10.0.25398.1486
    • Microsoft Windows Server 2025 lt 10.0.26100.0..10.0.26100.3476
    • Microsoft Windows Server 2025 (Server Core installation) lt 10.0.26100.0..10.0.26100.3476
    Fixed in
    • Microsoft Windows 10 Version 1507 10.0.10240.20947
    • Microsoft Windows 10 Version 1607 10.0.14393.7876
    • Microsoft Windows 10 Version 1809 10.0.17763.7009
    • Microsoft Windows 10 Version 21H2 10.0.19044.5608
    • Microsoft Windows 10 Version 22H2 10.0.19045.5608
    • Microsoft Windows 11 version 22H2 10.0.22621.5039
    • Microsoft Windows 11 version 22H3 10.0.22631.5039
    • Microsoft Windows 11 Version 23H2 10.0.22631.5039
    • Microsoft Windows 11 Version 24H2 10.0.26100.3476
    • Microsoft Windows Server 2008 R2 Service Pack 1 6.1.7601.27618
    • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) 6.1.7601.27618
    • Microsoft Windows Server 2008 Service Pack 2 6.0.6003.23168
    • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) 6.0.6003.23168
    • Microsoft Windows Server 2012 6.2.9200.25368
    • Microsoft Windows Server 2012 (Server Core installation) 6.2.9200.25368
    • Microsoft Windows Server 2012 R2 6.3.9600.22470
    • Microsoft Windows Server 2012 R2 (Server Core installation) 6.3.9600.22470
    • Microsoft Windows Server 2016 10.0.14393.7876
    • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.7876
    • Microsoft Windows Server 2019 10.0.17763.7009
    • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.7009
    • Microsoft Windows Server 2022 10.0.20348.3328
    • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.1486
    • Microsoft Windows Server 2025 10.0.26100.3476
    • Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.3476

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.0

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.0

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: pwn.watch, Msrc Update Guide, CVE.org

    30.4 %

    EPSS score

    Elevated — model estimates 10-50% exploitation likelihood.

    Source: FIRST EPSS, percentile 98.2

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    245.36 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.0 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    30.4 %
    Elevated — model estimates 10-50% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    98.2
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 13 March 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-707

    Response and mitigation

    Why act now?

    Prioritisation rationale

    Exploitation needs user interaction and local execution. Its value to attackers is bypassing the security prompts and internet-file protections that should stop untrusted consoles: a crafted .msc is delivered via phishing or fake software downloads and then runs code without an effective warning. CISA flags it for known ransomware campaign use, and its exploitation likelihood ranks among the highest of all scored CVEs. Organisations with large office-client fleets, widespread local admin rights and weak attachment filtering are the most exposed. Treat it as an emergency client patch (≤ 7 days), apply the .msc blocking immediately, and score it above its moderate base severity because of the ransomware context.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Deploy the March 2025 Patch Tuesday update (11 March 2025) as a priority. Minimum target builds per the context: Windows 10 1507 → 10.0.10240.20947, 1607 → 10.0.14393.7876, 1809 → 10.0.17763.7009, 21H2 → 10.0.19044.5608. Look up the per-edition KB number in the Microsoft Security Update Guide entry for CVE-2025-26633. Check there as well for coverage of Windows 11, Windows Server and any ESU-only systems.
      • Verify patch status. Use Intune, SCCM or Defender Vulnerability Management to find every client below those builds. Compare the build against (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').UBR. Remediate unpatched admin workstations and jump hosts first.
      • Block .msc files at the perimeter. Strip or quarantine .msc attachments at the mail gateway, including inside ZIP, RAR and ISO containers. Block .msc downloads at the web proxy. There is virtually no legitimate business need for externally sourced MMC consoles.
      • Start a compromise assessment. Run a 30-day retro-hunt in EDR and SIEM (see "Detection rules"). Look for:
        • mmc.exe opening .msc files from download, temp or archive paths,
        • .msc files inside locale folders such as System32\en-US\ or System32\de-DE\,
        • directories named C:\Windows \ with a trailing space.
      • Isolate affected hosts and reset credentials. Network-isolate hits via EDR. Reset credentials for users logged on to those hosts and revoke browser sessions and tokens. This CVE is used in ransomware operations, typically followed by an infostealer or backdoor payload.

    2. Runbook step 2

      Mitigation layers

      • Endpoint hardening (application control): Use WDAC or AppLocker to deny mmc.exe to standard users, or allow only signed snap-ins from %SystemRoot%\System32. For non-admins, also use GPO to remap the .msc file association to notepad.exe.
      • Filesystem ACLs: Remove "Create folders" for Authenticated Users on the root of C:\. This prevents spoofed paths such as C:\Windows \System32\. Test installer compatibility first.
      • Mail and web protection: Enforce Mark-of-the-Web and keep SmartScreen on. Run these Defender ASR rules in block mode:
        • "Block executable content from email client and webmail",
        • "Block executable files from running unless they meet a prevalence, age, or trusted list criterion".
      • IAM and least privilege: Remove local admin rights. Restrict administrative MMC usage to hardened Privileged Access Workstations. Standard users do not need MMC.
      • Network segmentation: Block outbound internet traffic from mmc.exe via host firewall or EDR network protection. MMC has no legitimate reason to reach internet destinations.

    3. Runbook step 3

      Detection rules

      • Sysmon EID 1 / Security EID 4688: Image ends with \mmc.exe and CommandLine references a .msc in a user-writable path. KQL: DeviceProcessEvents | where FileName =~ "mmc.exe" and ProcessCommandLine has ".msc" and ProcessCommandLine has_any ("\\Downloads\\","\\Temp\\","\\AppData\\","\\Users\\Public\\")
      • Suspicious process ancestry (EDR): mmc.exe spawning powershell.exe, cmd.exe, mshta.exe, rundll32.exe, wscript.exe or curl.exe. Sigma shape: ParentImage|endswith: '\mmc.exe' AND Image|endswith: [...]. Triage these hits at high priority.
      • Sysmon EID 11 / Security EID 4663 (file creation): TargetFilename matching C:\Windows\System32\??-??\*.msc or C:\Windows \*, where the creating process is neither TrustedInstaller.exe nor msiexec.exe. This is the core MUI-path abuse pattern.
      • Sysmon EID 3 / Zeek conn.log: mmc.exe connecting to public IP addresses, especially HTTP(S) fetches immediately after a .msc is opened.
      • Proxy and mail logs: Downloads or attachments ending in .msc, or archives containing .msc. SPL: index=proxy uri_path="*.msc" | stats count by src_ip, url

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

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

    Source: pwn.watch, Microsoft Security Update Guide, NVD (NIST), CISA KEV Catalog, cvelistv5, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    MicrosoftWindows 10 Version 1507
    • 10.0.10240.0 – < 10.0.10240.20947
    • 10.0.10240.20947
    MicrosoftWindows 10 Version 1607
    • 10.0.14393.0 – < 10.0.14393.7876
    • 10.0.14393.7876
    MicrosoftWindows 10 Version 1809
    • 10.0.17763.0 – < 10.0.17763.7009
    • 10.0.17763.7009
    MicrosoftWindows 10 Version 21H2
    • 10.0.19044.0 – < 10.0.19044.5608
    • 10.0.19044.5608
    MicrosoftWindows 10 Version 22H2
    • 10.0.19045.0 – < 10.0.19045.5608
    • 10.0.19045.5608
    MicrosoftWindows 11 version 22H2
    • 10.0.22621.0 – < 10.0.22621.5039
    • 10.0.22621.5039
    MicrosoftWindows 11 version 22H3
    • 10.0.22631.0 – < 10.0.22631.5039
    • 10.0.22631.5039
    MicrosoftWindows 11 Version 23H2
    • 10.0.22631.0 – < 10.0.22631.5039
    • 10.0.22631.5039
    MicrosoftWindows 11 Version 24H2
    • 10.0.26100.0 – < 10.0.26100.3476
    • 10.0.26100.3476
    MicrosoftWindows Server 2008 R2 Service Pack 1
    • 6.1.7601.0 – < 6.1.7601.27618
    • 6.1.7601.27618
    MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)
    • 6.1.7601.0 – < 6.1.7601.27618
    • 6.1.7601.27618
    MicrosoftWindows Server 2008 Service Pack 2
    • 6.0.6003.0 – < 6.0.6003.23168
    • 6.0.6003.23168
    MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)
    • 6.0.6003.0 – < 6.0.6003.23168
    • 6.0.6003.23168
    MicrosoftWindows Server 2012
    • 6.2.9200.0 – < 6.2.9200.25368
    • 6.2.9200.25368
    MicrosoftWindows Server 2012 (Server Core installation)
    • 6.2.9200.0 – < 6.2.9200.25368
    • 6.2.9200.25368
    MicrosoftWindows Server 2012 R2
    • 6.3.9600.0 – < 6.3.9600.22470
    • 6.3.9600.22470
    MicrosoftWindows Server 2012 R2 (Server Core installation)
    • 6.3.9600.0 – < 6.3.9600.22470
    • 6.3.9600.22470
    MicrosoftWindows Server 2016
    • 10.0.14393.0 – < 10.0.14393.7876
    • 10.0.14393.7876
    MicrosoftWindows Server 2016 (Server Core installation)
    • 10.0.14393.0 – < 10.0.14393.7876
    • 10.0.14393.7876
    MicrosoftWindows Server 2019
    • 10.0.17763.0 – < 10.0.17763.7009
    • 10.0.17763.7009
    MicrosoftWindows Server 2019 (Server Core installation)
    • 10.0.17763.0 – < 10.0.17763.7009
    • 10.0.17763.7009
    MicrosoftWindows Server 2022
    • 10.0.20348.0 – < 10.0.20348.3328
    • 10.0.20348.3328
    MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)
    • 10.0.25398.0 – < 10.0.25398.1486
    • 10.0.25398.1486
    MicrosoftWindows Server 2025
    • 10.0.26100.0 – < 10.0.26100.3476
    • 10.0.26100.3476
    MicrosoftWindows Server 2025 (Server Core installation)
    • 10.0.26100.0 – < 10.0.26100.3476
    • 10.0.26100.3476

    Vendors and products

    Affected operating systems

    Affected operating systems
    Windowsmicrosoftwindows_10_1507—
    Windowsmicrosoftwindows_10_1607—
    Windowsmicrosoftwindows_10_1809—
    Windowsmicrosoftwindows_10_21h2—
    Windowsmicrosoftwindows_10_22h2—
    Windowsmicrosoftwindows_11_22h2—
    Windowsmicrosoftwindows_11_23h2—
    Windowsmicrosoftwindows_11_24h2—
    Windowsmicrosoftwindows_server_2008r2
    Windowsmicrosoftwindows_server_2008—
    Windowsmicrosoftwindows_server_2012r2
    Windowsmicrosoftwindows_server_2012—
    Windowsmicrosoftwindows_server_2016—
    Windowsmicrosoftwindows_server_2019—
    Windowsmicrosoftwindows_server_2022—
    Windowsmicrosoftwindows_server_2022_23h2—
    Windowsmicrosoftwindows_server_2025—

    Weakness classes (CWE)

    • CWE-707Improper Neutralization

      Pillar

      The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being read from an upstream component or sent to a downstream component.

      Entry at MITRE CWE-707

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    One NVD translation into another language is hidden.

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-26633
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-26633"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-26633.svg?lang=en" alt="CVE-2025-26633 – NEOSEC Intel" height="20"></a>