CVE Tools

CVE-2025-26633

Microsoft Management Console Security Feature Bypass Vulnerability

Exploited in the wild. In CISA KEV since 2025‑03‑11. Fixed versions are out.

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Microsoft Windows 10 Version 1507Affected: ≥ 10.0.10240.0, < 10.0.10240.20947Upgrade to: 10.0.10240.20947Affected: ≥ 10.0.14393.0, < 10.0.14393.7876Upgrade to: 10.0.14393.7876Affected: ≥ 10.0.17763.0, < 10.0.17763.7009Upgrade to: 10.0.17763.7009Affected: ≥ 10.0.19044.0, < 10.0.19044.5608Upgrade to: 10.0.19044.5608 + 1 more branchStated by: CVE record
  • Microsoft Windows 11 version 22H2Affected: ≥ 10.0.22621.0, < 10.0.22621.5039Upgrade to: 10.0.22621.5039Affected: ≥ 10.0.22631.0, < 10.0.22631.5039Upgrade to: 10.0.22631.5039Affected: ≥ 10.0.26100.0, < 10.0.26100.3476Upgrade to: 10.0.26100.3476Stated by: CVE record
  • Microsoft Windows Server 2008 R2 Service Pack 1Affected: ≥ 6.1.7601.0, < 6.1.7601.27618Upgrade to: 6.1.7601.27618Stated by: CVE record
  • Microsoft Windows Server 2008 Service Pack 2Affected: ≥ 6.0.6003.0, < 6.0.6003.23168Upgrade to: 6.0.6003.23168Stated by: CVE record
  • Microsoft Windows Server 2012Affected: ≥ 6.2.9200.0, < 6.2.9200.25368Upgrade to: 6.2.9200.25368Stated by: CVE record

Versions as the sources state them. 5 more products have version data. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Identify whether any systems are running an affected Windows version (Windows Server 2008/2008 R2/2012/2012 R2/2016/2019/2022/2025, Windows 10, Windows 11).
  2. On each affected system, check whether it has been updated past the fixed build for your exact version (see step 4 for the fixed versions).
  3. If a system is missing the fix, plan a maintenance window and apply Microsoft’s update that addresses CVE-2025-26633 using Windows Update or the Microsoft update guide.
  4. Upgrade/patch to the fixed version for your OS:
    • Windows 10: 10.0.10240.20947 or 10.0.14393.7876 or 10.0.17763.7009 or 10.0.19044.5608 or 10.0.19045.5608
    • Windows 11: 10.0.22621.5039 or 10.0.22631.5039 or 10.0.26100.3476
    • Windows Server 2008 R2: 6.1.7601.27618
    • Windows Server 2008: 6.0.6003.23168
    • Windows Server 2012: 6.2.9200.25368
    • Windows Server 2012 R2: 6.3.9600.22470

Coverage timeline

0 publishers
  1. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened. 1 further article named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

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

In plain language

Written by AI from the record

CVE-2025-26633 is a Windows issue that can let attackers bypass a security feature in Microsoft Management Console, and it’s being used in real ransomware activity—so affected Windows systems should be updated or mitigations applied immediately.

CVE-2025-26633 is a Microsoft Management Console security feature bypass due to improper neutralization that allows a local attacker to evade an intended security control; the vulnerability is listed in CISA KEV as exploited in ransomware campaigns.

If you're affected

  • Remote access to your systems
  • Ransomware infection risk
  • Server and workstation disruption
  • Credential and data compromise

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS98th
Public exploit
CISA KEV
CISA KEV

Listed as exploited in the wild since 2025-03-11.

US federal agencies must remediate by 2025-04-01.

Known use in ransomware campaigns.

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

2 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

30% chance of exploitation activity in the next 30 days, which ranks it in the 98th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

The patch came 130 days before any public exploit.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. OpenVAS check added
  4. EPSS band changelow → moderate
  5. Public exploit / PoCsource: other
  6. Patch availablerecord updated

Affected products

Technical detail

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Scored 7.0 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Windows 10 Version 1507, not every advisory. This one: actively exploited.