dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-62455

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 Message Queuing 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 Message Queuing (MSMQ) contains an improper input validation flaw that allows a locally authenticated attacker with existing authorization to execute code at a higher privilege level, potentially achieving local privilege escalation through malformed message parameters.

MitigationApply the relevant Microsoft security patch for CVE-2025-62455 through Windows Update or your patch management system, and verify MSMQ services function correctly post-update.

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 Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.8688
Windows Server 2019Operating system
Affected:< 10.0.17763.8146

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. Verify MSMQ is installed or enabled
    Run 'Get-WindowsOptionalFeature -Online -FeatureName MSMQ' in PowerShell, or check via Control Panel > Programs > Windows Features > Microsoft Message Queue (MSMQ) Server
    Affected if MSMQ feature is found and state is Enabled
  2. Confirm Windows build version
    Run 'winver' or 'systeminfo | findstr "Build"' to obtain the OS build number, then compare against the affected ranges: 10.0.14393.8688 (Windows 10 1607, Server 2016), 10.0.17763.8146 (Windows 10 1809, Server 2019), 10.0.19044.6691 (Windows 10 21h2), 10.0.19045.6691 (Windows 10 22h2)
    Affected if Installed Windows build is lower than the corresponding threshold for your Windows version
  3. Check if MSMQ service is running
    Run 'Get-Service -Name MSMQ' in PowerShell or open Services.msc and locate the 'Message Queuing' service
    Affected if MSMQ service status is Running (the service must be active for the vulnerability to be exploitable)

You are affected if MSMQ is installed/enabled, your Windows build is below the specified threshold for your version, and the MSMQ service is currently running.

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 relevant Microsoft security patch for CVE-2025-62455 through Windows Update or your patch management system, and verify MSMQ services function correctly post-update.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.8688 or later | Windows 10 1809: build 10.0.17763.8146 or later | Windows 10 21h2: build 10.0.19044.6691 or later | Windows 10 22h2: build 10.0.19045.6691 or later | Windows Server 2016: build 10.0.14393.8688 or later | Windows Server 2019: build 10.0.17763.8146 or

  1. Identify the Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine if Windows Message Queuing (MSMQ) feature is enabled - check via Control Panel > Programs and Features > Turn Windows features on or off
  3. For Windows 10 1607 systems: Apply security update KB5055520 or later to reach build 10.0.14393.8688
  4. For Windows 10 1809 systems: Apply security update KB5055523 or later to reach build 10.0.17763.8146
  5. For Windows 10 21h2 systems: Apply security update KB5055527 or later to reach build 10.0.19044.6691
  6. For Windows 10 22h2 systems: Apply security update KB5055525 or later to reach build 10.0.19045.6691
  7. For Windows Server 2016: Apply security update KB5055520 to reach build 10.0.14393.8688
  8. For Windows Server 2019: Apply security update KB5055523 to reach build 10.0.17763.8146
Caveat Windows Server 2008 and 2012 are end-of-life with no security updates; requires operating system migration to supported version

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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