dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-27914

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.14393.9060 / 10.0.17763.8644 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Improper access control in Microsoft Management Console allows an authorized attacker to elevate privileges locally.

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 confidence

This is a local privilege escalation vulnerability in Microsoft Management Console (MMC) caused by improper access control. An attacker who already has authorized access to the system can exploit this vulnerability to gain higher privileges locally. The vulnerability affects how MMC handles access to certain snap-ins or operations.

MitigationApply the Microsoft security update for this vulnerability when released, and ensure users follow the principle of least privilege when assigning MMC-related permissions.

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
Windows 10 1607Operating system
Affected:< 10.0.14393.9060
Windows 10 1809Operating system
Affected:< 10.0.17763.8644
Windows 10 21h2Operating system
Affected:< 10.0.19044.7184
Windows 10 22h2Operating system
Affected:< 10.0.19045.7184
Windows 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836

CVSS 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Open Settings > System > About, or run 'winver' command, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt
    Affected if The displayed version matches any of the affected Windows 10 or Windows 11 versions listed with a build number lower than the corresponding threshold (10.0.14393.9060, 10.0.17763.8644, 10.0.19044.7184, 10.0.19045.7184, 10.0.22631.6936, 10.0.26100.8246, 10.0.26200.8246, or 10.0.28000.1836)
  2. Confirm Windows 10 build for version 1607
    If running Windows 10 1607, run 'winver' or check systeminfo to get the exact build number (e.g., 10.0.14393.x)
    Affected if Build number is below 10.0.14393.9060
  3. Confirm Windows 10 build for version 1809
    If running Windows 10 version 1809, check the build number in winver or systeminfo
    Affected if Build number is below 10.0.17763.8644
  4. Confirm Windows 10 build for versions 21h2 and 22h2
    If running Windows 10 version 21h2 or 22h2, verify the build number shown in winver or Settings > About
    Affected if Build number is below 10.0.19044.7184 (21h2) or below 10.0.19045.7184 (22h2)
  5. Confirm Windows 11 build for versions 23h2, 24h2, 25h2, and 26h1
    If running Windows 11, run 'winver' to identify the specific version (23h2, 24h2, 25h2, or 26h1) and note the build number
    Affected if Build number is below 10.0.22631.6936 (23h2), 10.0.26100.8246 (24h2), 10.0.26200.8246 (25h2), or 10.0.28000.1836 (26h1)

The system is affected if it is running any of the listed Windows versions with a build number lower than the corresponding fixed build number for that version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.14393.9060 / 10.0.17763.8644 / 10.0.19044.7184 or later
Fixed in 10.0.14393.906010.0.17763.864410.0.19044.7184
Interim mitigation

Apply the Microsoft security update for this vulnerability when released, and ensure users follow the principle of least privilege when assigning MMC-related permissions.

Recommended fix High confidence

Apply the appropriate Windows cumulative security update for your specific Windows version that includes the fix for CVE-2026-27914 in Microsoft Management Console

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which version range your system falls into from the affected versions list
  3. Apply the appropriate Windows Security Update that contains the fix for this vulnerability
  4. For Windows 10 1607: Upgrade to build 10.0.14393.9060 or later
  5. For Windows 10 1809: Upgrade to build 10.0.17763.8644 or later
  6. For Windows 10 21h2: Upgrade to build 10.0.19044.7184 or later
  7. For Windows 10 22h2: Upgrade to build 10.0.19045.7184 or later
  8. For Windows 11 23h2: Upgrade to build 10.0.22631.6936 or later
Caveat Standard Windows update deployment considerations apply - ensure backups and test in non-production environments first, though cumulative updates typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27914 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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