CVE-2025-53143
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 · uneditedAccess 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 confidenceA type confusion vulnerability in Windows Message Queuing (MSMQ) allows an authenticated attacker to execute arbitrary code by sending specially crafted MSMQ messages over the network. The flaw occurs when the service improperly handles objects of incompatible types, leading to memory corruption that can be leveraged for remote code execution.
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< 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.4851CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify MSMQ service is installedOpen Services (services.msc) and look for 'Message Queuing' service, or run: Get-Service -Name MSMQ in PowerShellAffected if MSMQ service exists on the system - vulnerability applies only if MSMQ is installed
-
Confirm MSMQ service is runningRun: Get-Service -Name MSMQ | Select-Object Status, StartType. Check if Status is 'Running'Affected if Service is running - the vulnerability is only exploitable when the MSMQ service is active
-
Check Windows build versionRun: winver or Get-ComputerInfo | Select-Object WindowsVersion, OsBuildNumber. Compare against affected builds: Windows 10 1507 < 10240.21100, 1607 < 14393.8330, 1809 < 17763.7678, 21h2 < 19044.6216, 22h2 < 19045.6216; Windows 11 22h2 < 22621.5768, 23h2 < 22631.5768, 24h2 < 26100.4851Affected if Installed build number falls below the fixed version for that Windows release
-
Verify MSMQ network listener statusRun: netstat -an | findstr :1801 or check MSMQ properties in Computer Management > Services and Applications > Message Queuing > outgoing queues or listen for incoming connectionsAffected if MSMQ is listening on port 1801/TCP - indicates the service is accepting network messages where exploitation could occur
System is affected if MSMQ service is installed and running, Windows build is below the fixed version for that release, and MSMQ accepts network connections on port 1801.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2110010.0.14393.833010.0.17763.7678
Apply the Microsoft security update for CVE-2025-53143 when released. Until then, restrict network access to MSMQ ports (1801, TCP) to trusted systems only, or disable MSMQ if not required by the environment.
Upgrade to the minimum fixed build for your Windows release: Windows 10 1507 to 10.0.10240.21100, Windows 10 1607 to 10.0.14393.8330, Windows 10 1809 to 10.0.17763.7678, Windows 10 21h2 to 10.0.19044.6216, Windows 10 22h2 to 10.0.19045.6216, Windows 11 22h2 to 10.0.22621.5768, Windows 11 23h2 to 10.
- Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Identify which Windows 10 or 11 release channel you are on (1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2/23h2/24h2)
- Run Windows Update (Settings > Update & Security > Windows Update) to install the latest security updates
- Alternatively, manually install the corresponding cumulative update for your Windows version that includes KB5055527 (or later) from the Microsoft Update Catalog
- Verify the update was successful by checking that the build number matches or exceeds the fixed version for your release
- Restart the system when prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53143 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-53143 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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