CVE-2025-26633
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper neutralization in Microsoft Management Console allows an unauthorized attacker to bypass a security feature locally.
In the news
Third-party coverage- Russian Group EncryptHub Exploits MSC EvilTwin Vulnerability to ...
- Russian threat actor weaponized Microsoft Management Console flaw
- Russian Hackers Exploit CVE-2025-26633 via MSC EvilTwin ...
- CVE-2025-26633 Archives - SecurityWeek
- Microsoft Flags Six Active Zero-Days, Patches 57 Flaws: Patch Tuesday
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability in Microsoft Management Console involves improper neutralization of input, allowing a local attacker to bypass a security feature. The issue stems from insufficient sanitization of input within MMC that could enable an unauthorized user to circumvent security controls through local access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 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.3403CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Windows version against affected rangesOpen Command Prompt or PowerShell and run `winver` to see the full version number and build, or use `systeminfo | findstr /B /C:"OS Version"`. For PowerShell, run `Get-ComputerInfo | Select-Object WindowsVersion,OsVersion,OsBuildNumber`Affected if The displayed Windows version falls below any of these thresholds: Windows 10 1507 < 10.0.10240.20947, Windows 10 1607 < 10.0.14393.7876, Windows 10 1809 < 10.0.17763.7009, Windows 10 21h2 < 10.0.19044.5608, Windows 10 22h2 < 10.0.19045.5608, Windows 11 22h2 < 10.0.22621.5039, Windows 11 23h2 < 10.0
-
Confirm Windows 10 release versionIf running Windows 10, run `winver` to see which release (1507, 1607, 1809, 21h2, or 22h2) is installed. The release is displayed in the first line of the About Windows dialogAffected if The release shown is 1507, 1607, 1809, 21h2, or 22h2 and its build number is below the corresponding threshold for that release
-
Verify MMC component is presentConfirm mmc.exe exists on the system by checking `C:\Windows\System32\mmc.exe` or running `Test-Path C:\Windows\System32\mmc.exe` in PowerShellAffected if MMC is installed on the system and the Windows version is in the affected range
You are affected if your Windows version is below any of the listed build thresholds AND the MMC component is present on your system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.10240.2094710.0.14393.787610.0.17763.7009
Apply Microsoft security updates for CVE-2025-26633 when available through Windows Update or Microsoft Update catalog. Verify that the specific security feature bypass is mitigated through testing after patching.
Install the appropriate Windows security update containing the CVE-2025-26633 fix from Windows Update or Microsoft Update Catalog for your specific Windows version
- Open Windows Settings and navigate to Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest security updates
- Ensure the update includes the fix for CVE-2025-26633 (Microsoft Management Console security feature bypass)
- Restart the computer if prompted to complete the installation
- Verify the installed Windows version matches or exceeds the fixed release numbers: Windows 10 1507: 10.0.10240.20947, Windows 10 1607: 10.0.14393.7876, Windows 10 1809: 10.0.17763.7009, Windows 10 21h2: 10.0.19044.5608, Windows 10 22h2: 10.0.19045.5608, Windows 11 22h2: 10.0.22621.5039, Windows 11 23h2: 10.0.22631.5039, Windows 11 24h2: 10.0.26100.3403
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26633 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26633 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data