Skip to content
Fencer Intel
high 8.8

CVE-2025-53145 json

Microsoft Message Queuing (MSMQ) Remote Code Execution Vulnerability

published last yr. modified 4mo ago also EUVD-2025-24322

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
8.5%
EPSS 8.5% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

Access of resource using incompatible type ('type confusion') in Windows Message Queuing allows an authorized attacker to execute code over a network.

Patch / fix

  • Microsoft Windows 10 Version 1507 10.0.10240.21100
  • Microsoft Windows 10 Version 1607 10.0.14393.8330
  • Microsoft Windows 10 Version 1809 10.0.17763.7678
  • Microsoft Windows 10 Version 21H2 10.0.19044.6216
  • Microsoft Windows 10 Version 22H2 10.0.19045.6216
  • Microsoft Windows 11 version 22H2 10.0.22621.5768
  • Microsoft Windows 11 version 22H3 10.0.22631.5768
  • Microsoft Windows 11 Version 23H2 10.0.22631.5768
  • Microsoft Windows 11 Version 24H2 10.0.26100.4946
  • Microsoft Windows Server 2008 R2 Service Pack 1 6.1.7601.27872
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) 6.1.7601.27872
  • Microsoft Windows Server 2008 Service Pack 2 6.0.6003.23471
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) 6.0.6003.23471
  • Microsoft Windows Server 2012 6.2.9200.25622
  • Microsoft Windows Server 2012 (Server Core installation) 6.2.9200.25622
  • Microsoft Windows Server 2012 R2 6.3.9600.22725
  • Microsoft Windows Server 2012 R2 (Server Core installation) 6.3.9600.22725
  • Microsoft Windows Server 2016 10.0.14393.8330
  • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.8330
  • Microsoft Windows Server 2019 10.0.17763.7678
  • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.7678
  • Microsoft Windows Server 2022 10.0.20348.4052
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.1791
  • Microsoft Windows Server 2025 10.0.26100.4946
  • Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.4946

Is CVE-2025-53145 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

8.49% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Windows 10 Version 1507
  • Microsoft Windows 10 Version 1607
  • Microsoft Windows 10 Version 1809
  • Microsoft Windows 10 Version 21H2
  • Microsoft Windows 10 Version 22H2
  • Microsoft Windows 11 version 22H2
  • Microsoft Windows 11 version 22H3
  • Microsoft Windows 11 Version 23H2
  • Microsoft Windows 11 Version 24H2
  • Microsoft Windows Server 2008 R2 Service Pack 1
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
  • Microsoft Windows Server 2008 Service Pack 2
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 (Server Core installation)
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2012 R2 (Server Core installation)
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2016 (Server Core installation)
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2019 (Server Core installation)
  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • Microsoft Windows Server 2025
  • Microsoft Windows Server 2025 (Server Core installation)

Classification

Weakness
  • CWE-843 Access of Resource Using Incompatible Type

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.