dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-27910

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 handling of insufficient permissions or privileges in Windows Installer 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

Windows Installer contains a flaw where improper handling of permission checks allows a locally authenticated attacker to elevate their privileges to higher integrity levels. The vulnerability stems from insufficient validation of user privileges during certain Windows Installer operations, enabling a user with limited rights to gain administrative access.

MitigationApply the relevant Microsoft security patch for Windows Installer when released. Prioritize patching domain controllers and systems with sensitive data or external exposure. Verify privilege boundaries after patching.

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. Check Windows version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine your Windows build number
    Affected if Your build number falls below the patch version listed for your Windows release (e.g., < 10.0.14393.9060 for Windows 10 1607)
  2. Verify Windows Installer service is present
    Open Services (services.msc) or run 'sc query msiserver' to check if the Windows Installer service exists
    Affected if The Windows Installer service is present and enabled on the system
  3. Confirm local user account context
    Run 'whoami /groups' to see your current user group memberships and integrity level
    Affected if You are running as a standard user or low-privilege account on an unpatched Windows version
  4. Check for available privilege escalation vectors
    Review installed software packages and recent MSI installations via 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select DisplayName, DisplayVersion'
    Affected if MSI packages have been installed by users with limited privileges on an unpatched system

You are affected if your Windows build number is below the threshold for your Windows release AND you have standard user accounts on the system that could be exploited for privilege escalation via Windows Installer.

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 relevant Microsoft security patch for Windows Installer when released. Prioritize patching domain controllers and systems with sensitive data or external exposure. Verify privilege boundaries after patching.

Recommended fix High confidence

Windows 10/11 with the minimum build numbers specified above (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 depending on version)

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or 11 version and build you are currently running
  3. For Windows 10 1607: Upgrade to build 10.0.14393.9060 or later
  4. For Windows 10 1809: Upgrade to build 10.0.17763.8644 or later
  5. For Windows 10 21h2: Upgrade to build 10.0.19044.7184 or later
  6. For Windows 10 22h2: Upgrade to build 10.0.19045.7184 or later
  7. For Windows 11 23h2: Upgrade to build 10.0.22631.6936 or later
  8. For Windows 11 24h2: Upgrade to build 10.0.26100.8246 or later
Caveat Standard Windows update risks - ensure backups and compatibility testing for critical systems before deployment

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27910 — 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-27910 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