dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-53144

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

Type confusion vulnerability in Windows Message Queuing (MSMQ) allows an authenticated attacker to achieve remote code execution by sending specially crafted network messages to the MSMQ service.

MitigationApply the Microsoft security update for CVE-2025-53144 to all affected Windows systems running Message Queuing services, and review MSMQ configurations to limit network exposure.

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 MSMQ service is installed
    Open Services (services.msc) and look for 'Message Queuing' service, or run: Get-Service | Where-Object {$_.Name -like '*MSMQ*'}
    Affected if The Message Queuing service is present on the system
  2. Check Windows version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' and compare the build number to the vulnerable versions listed (10.0.10240.21100, 10.0.14393.8330, 10.0.17763.7678, 10.0.19044.6216, 10.0.19045.6216, 10.0.22621.5768, 10.0.22631.5768, 10.0.26100.4851)
    Affected if The installed Windows build number is lower than any of the listed version thresholds for the corresponding Windows release
  3. Confirm MSMQ service is running
    Run 'Get-Service MSMQ' or check if the MSMQ service status is 'Running' in services.msc
    Affected if The MSMQ service is currently running
  4. Check MSMQ network listener status
    Run 'netstat -an | findstr "1801"' or use PowerShell: Get-NetTCPConnection -LocalPort 1801 -ErrorAction SilentlyContinue
    Affected if MSMQ is listening on TCP port 1801 (indicating network-facing exposure)

A system is affected if it runs a vulnerable Windows version with the MSMQ service installed and running, particularly if the service is exposed to the network on port 1801.

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-53144 to all affected Windows systems running Message Queuing services, and review MSMQ configurations to limit network exposure.

Recommended fix High confidence

Windows 10 1507 to build >=10.0.10240.21100 | Windows 10 1607 to build >=10.0.14393.8330 | Windows 10 1809 to build >=10.0.17763.7678 | Windows 10 21h2 to build >=10.0.19044.6216 | Windows 10 22h2 to build >=10.0.19045.6216 | Windows 11 22h2 to build >=10.0.22621.5768 | Windows 11 23h2 to build >=10

  1. Identify the current Windows version by going to Settings > System > About
  2. Determine which Windows 10 or 11 release channel you are on (1507, 1607, 1809, 21h2, 22h2, 22h2 for Windows 11, 23h2, or 24h2)
  3. Check if your current build number is less than the fixed version for your release: 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)
  4. Open Windows Update (Settings > Update & Security > Windows Update) and install all available security updates
  5. Alternatively, download the applicable security update from the Microsoft Update Catalog for your specific Windows version
  6. Restart the computer after the update installation completes
  7. Verify the installed build number meets or exceeds the required fixed version
Caveat Standard Windows cumulative update apply; no major functional changes expected beyond security fixes

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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