dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-50177

HIGH · 8.1 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.10240.21100 / 10.0.14393.8330 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Use after free in Windows Message Queuing allows an unauthorized attacker to execute code over a network.

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

A use-after-free vulnerability exists in Windows Message Queuing (MSMQ) that allows an unauthenticated remote attacker to execute arbitrary code by sending specially crafted network packets to a target system with MSMQ enabled.

MitigationApply the Microsoft security update for CVE-2025-50177 to all affected Windows systems, and consider disabling Windows Message Queuing if not required in the environment.

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 1507Operating system
Affected:< 10.0.10240.21100
Windows 10 1607Operating system
Affected:< 10.0.14393.8330
Windows 10 1809Operating system
Affected:< 10.0.17763.7678
Windows 10 21h2Operating system
Affected:< 10.0.19044.6216
Windows 10 22h2Operating system
Affected:< 10.0.19045.6216
Windows 11 22h2Operating system
Affected:< 10.0.22621.5768
Windows 11 23h2Operating system
Affected:< 10.0.22631.5768
Windows 11 24h2Operating system
Affected:< 10.0.26100.4851

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

CVSS:3.1/AV:N/AC:H/PR:N/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 if MSMQ service is installed
    Open Services console (services.msc) and look for 'Message Queuing' service, or run 'Get-Service -Name MSMQ' in PowerShell
    Affected if MSMQ service exists on the system - this is required for the vulnerability to be exploitable
  2. Check if MSMQ service is running
    Run 'Get-Service -Name MSMQ | Select-Object Status' in PowerShell or check the Status column in Services console
    Affected if MSMQ service is running - the vulnerability is only exploitable when the service is active
  3. Identify Windows version
    Run 'winver' command or 'Get-ComputerInfo | Select-Object OsVersion, OsBuildNumber' in PowerShell
    Affected if Windows version and build number fall within any of these ranges: Windows 10 1507 < 10.0.10240.21100, Windows 10 1607 < 10.0.14393.8330, Windows 10 1809 < 10.0.17763.7678, Windows 10 21h2 < 10.0.19044.6216, Windows 10 22h2 < 10.0.19045.6216, Windows 11 22h2 < 10.0.22621.5768, Windows 11 23h2 < 10.0.
  4. Confirm MSMQ network listener status
    Run 'netstat -an | findstr "1801"' in Command Prompt or use PowerShell 'Get-NetTCPConnection -LocalPort 1801 -ErrorAction SilentlyContinue' to check if MSMQ ports are listening
    Affected if MSMQ is listening on network ports (default port 1801) - this indicates the service is exposed to network traffic and could be remotely exploited

The system is affected if it runs a vulnerable Windows version (within the specified version ranges) AND has MSMQ service installed and running with network exposure.

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.10240.21100 / 10.0.14393.8330 / 10.0.17763.7678 or later
Fixed in 10.0.10240.2110010.0.14393.833010.0.17763.7678
Interim mitigation

Apply the Microsoft security update for CVE-2025-50177 to all affected Windows systems, and consider disabling Windows Message Queuing if not required in the environment.

Recommended fix High confidence

Windows 10 1507: build 10.0.10240.21100 or later | Windows 10 1607: build 10.0.14393.8330 or later | Windows 10 1809: build 10.0.17763.7678 or later | Windows 10 21h2: build 10.0.19044.6216 or later | Windows 10 22h2: build 10.0.19045.6216 or later | Windows 11 22h2: build 10.0.22621.5768 or later |

  1. Open Windows Settings by pressing Win+I
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Restart the computer if prompted to complete the installation
  5. Verify the installed build number matches or exceeds the fixed version for your Windows edition (Windows 10 1507: 10.0.10240.21100, Windows 10 1607: 10.0.14393.8330, Windows 10 1809: 10.0.17763.7678, Windows 10 21h2: 10.0.19044.6216, Windows 10 22h2: 10.0.19045.6216, Windows 11 22h2: 10.0.22621.5768, Windows 11 23h2: 10.0.22631.5768, Windows 11 24h2: 10.0.26100.4851)
  6. To check the build number: press Win+R, type 'winver', and press Enter
Caveat Standard Windows update; review known issues in Microsoft KB article before deployment in enterprise environments

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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