dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-62571

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.14393.8688 / 10.0.17763.8146 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 input validation 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

This is a local privilege escalation vulnerability in Windows Installer stemming from improper input validation. An attacker with low-level access can exploit insufficient validation of input data to elevate privileges to higher permissions on the local system.

MitigationApply the Microsoft security update for CVE-2025-62571 through standard Windows Update or patch management deployment, and verify the patch has been successfully installed.

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.8688
Windows 10 1809Operating system
Affected:< 10.0.17763.8146
Windows 10 21h2Operating system
Affected:< 10.0.19044.6691
Windows 10 22h2Operating system
Affected:< 10.0.19045.6691
Windows 11 23h2Operating system
Affected:< 10.0.22631.6345
Windows 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2008Operating system
Affected:all versions= r2

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
    Run 'winver' from command prompt or check System properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
    Affected if The displayed build number is lower than the fixed version for your Windows release (e.g., below 10.0.14393.8688 for Windows 10 1607, below 10.0.17763.8146 for Windows 10 1809, etc.)
  2. Confirm exact build via registry
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuildRevision'
    Affected if The combined build number (CurrentBuild.Revision) is lower than the patched version for your Windows release
  3. Check if security update KB5002xx is installed
    Run 'wmic qfe list' or 'Get-HotFix | Sort-Object InstalledOn' and look for a recent security update related to Windows Installer or CVE-2025-62571
    Affected if No recent Windows Installer or CVE-2025-62571 related security update appears in the installed updates list
  4. Verify Windows Installer service status
    Run 'sc query msiserver' to check if the Windows Installer service is present and running
    Affected if The service exists (which is default) - the vulnerability applies to any system with this component, regardless of service running state, as it can be invoked via MSI files
  5. Identify Windows edition
    Run 'systeminfo | findstr /C:"OS"' or check System properties to confirm if the system is Windows Server 2008 R2 specifically
    Affected if The system is Windows Server 2008 R2 (all versions are affected per the advisory)

The system is affected if it runs any of the listed Windows versions with a build number lower than the fixed version for that release, or if it is Windows Server 2008 R2, and the corresponding security update for CVE-2025-62571 has not been installed.

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.8688 / 10.0.17763.8146 / 10.0.19044.6691 or later
Fixed in 10.0.14393.868810.0.17763.814610.0.19044.6691
Interim mitigation

Apply the Microsoft security update for CVE-2025-62571 through standard Windows Update or patch management deployment, and verify the patch has been successfully installed.

Recommended fix High confidence

Install the January 2025 Windows Security Update (or later) - specific KB number varies by Windows version: KB5055528 (Windows 10 22h2/21h2), KB5055518 (Windows 11 23h2), KB5055520 (Windows 11 24h2/25h2), KB5055543 (Windows 10 1809), KB5055542 (Windows 10 1607)

  1. Open Windows Settings on the affected system
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest cumulative update
  4. Alternatively, manually download the security update from the Microsoft Update Catalog matching your Windows version (KB5055528 or later for Jan 2025 release)
  5. Restart the system after the update is installed
  6. Verify the installed version matches or exceeds the fixed build number for your Windows release
Caveat Ensure compatibility with existing line-of-business applications before deploying; Windows Server 2008 R2 is end-of-life and requires extended security updates or migration

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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