dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-53145

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
Remotely reachable 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
Access of resource using incompatible type ('type confusion') in Windows Message Queuing allows an authorized 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

This is a type confusion vulnerability in Windows Message Queuing (MSMQ) that allows an authenticated attacker to execute arbitrary code remotely over a network. The vulnerability stems from improper type handling when processing MSMQ messages, enabling code execution without requiring local access.

MitigationApply Microsoft security patches for Windows Message Queuing immediately, as this is a remote code execution vulnerability with high CVSS score. Verify MSMQ services are not exposed unnecessarily to untrusted networks.

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

CVSS:3.1/AV:N/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 if MSMQ feature is installed
    Open PowerShell and run: Get-WindowsOptionalFeature -Online -FeatureName MSMQ* | Where-Object {$_.State -eq 'Enabled'}
    Affected if MSMQ is installed and enabled; if not present, the system is not affected by this specific vulnerability
  2. Confirm Windows version falls within affected ranges
    Run 'winver' or in PowerShell: [System.Environment]::OSVersion.Version.ToString() and compare against the affected version ranges listed in the CVE
    Affected if Windows version is below 10.0.10240.21100 (Win10 1507), 10.0.14393.8330 (Win10 1607), 10.0.17763.7678 (Win10 1809), 10.0.19044.6216 (Win10 21h2), 10.0.19045.6216 (Win10 22h2), 10.0.22621.5768 (Win11 22h2), 10.0.22631.5768 (Win11 23h2), or 10.0.26100.4851 (Win11 24h2)
  3. Check if MSMQ service is running
    Run in PowerShell: Get-Service -Name MSMQ | Select-Object Status, Name, DisplayName
    Affected if MSMQ service is running; an attacker would need to send malicious MSMQ messages to trigger the vulnerability, so a stopped or disabled MSMQ service mitigates the risk

System is affected if it runs a vulnerable Windows version within the specified ranges AND has MSMQ feature installed and enabled, regardless of service state, as the vulnerability exists in the code path that processes MSMQ messages.

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 Microsoft security patches for Windows Message Queuing immediately, as this is a remote code execution vulnerability with high CVSS score. Verify MSMQ services are not exposed unnecessarily to untrusted networks.

Recommended fix High confidence

Upgrade to 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 la

  1. Open Settings > System > About to check the current Windows version and build number, or run 'winver' command
  2. If the build number is lower than the fixed version for your Windows release, open Windows Update (Settings > Update & Security > Windows Update)
  3. Click 'Check for updates' and install all available security updates
  4. Alternatively, manually download the specific security update from the Microsoft Update Catalog for your Windows version (search for CVE-2025-53145)
  5. After installation, restart the computer when prompted
  6. Verify the update was successful by checking the installed updates (run 'appwiz.cpl' and view installed updates) or checking the new build number
Caveat Standard Windows monthly cumulative updates; minimal risk as this is a security patch rather than a feature change

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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