Skip to main content

Windows Message Queuing CVE-2025-62455

HIGH
Improper Input Validation (CWE-20)
2025-12-09 secure@microsoft.com
7.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privilege local access
  2. Delivery
    Confirm MSMQ feature installed
  3. Exploit
    Send crafted input to Message Queuing service
  4. Execution
    Trigger improper input validation (CWE-20)
  5. Persist
    Execute code as SYSTEM
  6. Impact
    Full host compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Requires the Windows Message Queuing (MSMQ) feature to be installed and enabled on the target host - an optional Windows component that is NOT present in default installations. The attacker must already have local, low-privileged authenticated access (PR:L, AV:L) to run the exploit; no user interaction is needed (UI:N). It is not remotely exploitable over the network on its own and functions as a post-foothold privilege-escalation step. Affected platforms are Windows 10 (1607/1809/21H2/22H2) and Windows Server 2008/2008 R2/2012/2016/2019.

Impact

This is a genuine but not top-tier priority. The CVSS 3.1 vector (7.8 High, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) describes a local elevation-of-privilege flaw: an already-authenticated low-privileged user runs code that abuses improper input validation (CWE-20) in Windows Message Queuing (MSMQ) to gain full SYSTEM-level control (complete confidentiality, integrity, and availability impact). Because the attack vector is local and requires existing low-privilege access (PR:L), it is not remotely triggerable and is not a mass-exploitation candidate - it is a second-stage/post-compromise capability. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no signal of active exploitation or automatable weaponization; per the exploitation-status rules this is 'no public exploit identified at time of analysis.' No SSVC decision data was supplied. A conflicting signal to note: the input Tags label this 'Information Disclosure,' which contradicts the description and CVSS vector - this is an elevation-of-privilege issue (I:H/A:H, not confidentiality-only), so the tag is mislabeled. The real limiting factor is that MSMQ is an optional Windows component not installed by default, which substantially narrows the exposed population despite Windows itself being ubiquitous.

Exploit ScenarioDerived

An attacker who already has a low-privileged foothold on a Windows host where the MSMQ feature is installed (e.g., a standard user account or a compromised low-privilege service) sends crafted input to the Message Queuing service that fails input validation, corrupting execution to run attacker code with SYSTEM privileges. This turns a limited foothold into full host compromise. No public exploit code was identified at the time of analysis, and no user interaction is required.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 25, 2026

Local privilege escalation in Microsoft Windows Message Queuing (MSMQ) lets a low-privileged, authenticated user who can already log on to a host run crafted input against the MSMQ service and elevate to SYSTEM-level privileges (CVSS 3.1 base 7.8, AV:L/PR:L/UI:N, C:H/I:H/A:H). The exposure is limited by configuration: MSMQ is an optional Windows component that is not installed or enabled by default, so only hosts that have deliberately deployed the queue service are affected, and the flaw is not remotely exploitable on its own - it is a post-foothold escalation step that requires an existing local session. Affected platforms include Windows 10 1607, 1809, 21H2 and 22H2 and Windows Server 2008 SP2, 2008 R2 SP1, 2012, 2016 and 2019; no public exploit code has been identified at time of analysis and Microsoft's MSRC update guide entry is the authoritative remediation source. Overall this is a genuine but not top-tier priority: high impact if MSMQ is deployed, but gated behind local authenticated access and a non-default component.

RemediationAI

Apply the Microsoft security update for CVE-2025-62455 as published in the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-62455; the provided data does not include exact fixed KB or build numbers, so confirm the specific patch level for each affected platform (Windows 10 1607/1809/21H2/22H2 and Windows Server 2008/2008 R2/2012/2016/2019) directly from that advisory and prioritise MSMQ-enabled servers. Because exploitation requires the optional Message Queuing feature to be present, the strongest compensating control is to uninstall or disable it where it is not operationally required - via Windows Features ('Message Queuing') or the Server Manager role/feature removal - accepting that any application or legacy integration relying on MSMQ queues will stop functioning until the service is restored. Where MSMQ must remain enabled, reduce the local attack surface: restrict interactive and RDP logon to trusted administrators only, remove unnecessary local accounts and administrative group memberships so that a low-privileged foothold is harder to obtain (the PR:L precondition), and apply least-privilege hardening plus process and queue-monitoring on the MSMQ service (anomalous local calls, unexpected queue creation or message parsing crashes) since exploitation is a post-foothold escalation rather than a remote event. Blocking MSMQ network ports or disabling the RPC endpoint does not mitigate this issue, because the vector is AV:L and the flaw is triggered locally, so such network filtering should not be treated as a substitute for patching. Microsoft security updates are cumulative; also apply the corresponding monthly rollup/preview update for the platform branch in use so that adjacent MSMQ fixes are included.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is classified as CWE-20 (Improper Input Validation) in the Windows Message Queuing service, Microsoft's implementation of the MSMQ message-broker subsystem used for asynchronous, store-and-forward messaging between applications, services and (historically) across hosts via queues such as Direct, Private, Public, System and Dead Letter queues. MSMQ runs as a privileged Windows service and exposes interfaces that a local caller can reach; because the service does not adequately validate input supplied through that interface, a caller holding only local low-privileged credentials (PR:L) can reach code paths that execute in the service's elevated security context, yielding confidentiality, integrity and availability impact at C:H/I:H/A:H without user interaction (UI:N). The CVSS vector AV:L means the attack is launched from the local machine rather than across the network, and scope is unchanged (S:U), so the compromise is confined to the target host rather than a cross-boundary escape. CPE data pins the affected platform set to Microsoft Windows client and server operating systems - windows_10_1607, windows_10_1809, windows_10_21h2 and windows_10_22h2 (x86/x64), windows_server_2008 SP2 (x86/x64), windows_server_2008 R2 SP1, and windows_server_2012, with the accompanying tags also enumerating Windows Server 2016 and 2019. The practical attack surface therefore exists only where the Message Queuing feature has been installed and started, since default Windows installations do not include it.

Severity by source

Vendor (microsoft) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local low-privileged user exploits MSMQ input validation to reach SYSTEM, so AV:L/PR:L/UI:N with full C/I/A impact and unchanged scope; matches vendor vector.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Improper input validation in Windows Message Queuing allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

Microsoft Windows Message Queuing (MSMQ) carries a local privilege-escalation flaw, CVE-2025-62455, that allows a user who already holds a valid local session to escalate to SYSTEM-level control of the host. Exposure is limited to machines where the optional MSMQ component has been deliberately installed or enabled across Windows 10 (1607, 1809, 21H2, 22H2) and Windows Server 2008 SP2, 2008 R2 SP1, 2012, 2016 and 2019, so the affected population is a defined subset of the estate rather than the whole fleet. Leadership should care because on any MSMQ-enabled host this turns an ordinary compromised account into full administrative control, materially increasing the payoff of an initial foothold and the blast radius of credential theft in those segments.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: uninstall or disable the MSMQ optional component on hosts that do not require it; on hosts that must keep MSMQ, restrict local logon and administrative group membership to the minimum necessary accounts and enforce least-privilege separation between user and administrative sessions; monitor MSMQ service activity and privilege changes on affected systems; and track the Microsoft MSRC update guide entry as the authoritative remediation source until a patch is released.

Threat Intelligence Overview

EPSS Score
0.5%
Top 62% exploitable
Prevalence
Medium
Windows is ubiquitous but MSMQ is an optional, non-default component
Data Quality
2 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Affected Products (CPE)CVE.org

cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x64:*
cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x86:*
cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x64:*
cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x86:*
cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2008:-:sp2:*:*:*:*:x64:*
cpe:2.3:o:microsoft:windows_server_2008:-:sp2:*:*:*:*:x86:*
cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:*:*:*:*:x64:*
cpe:2.3:o:microsoft:windows_server_2012:-:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2012:r2:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2016:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2019:*:*:*:*:*:*:*:*
CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy