LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21290: Microsoft Message Queuing (MSMQ) Denial of Service Vulnerability

Microsoft Message Queuing (MSMQ) Denial of Service Vulnerability

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability can let an unauthenticated network attacker disrupt Microsoft Message Queuing on affected Windows systems. The business impact is service interruption, not data theft, based on the published CVSS impact. Prioritize systems where MSMQ supports business workflows or is reachable from untrusted networks.

Executive priority

High priority for environments using MSMQ in production, especially on servers supporting transaction, messaging, or application workflows. The expected harm is outage or degradation rather than data compromise. Patch and exposure reduction should be scheduled promptly within normal high-severity remediation timelines.

Technical view

CVE-2025-21290 is a Microsoft Message Queuing denial-of-service issue rated CVSS 7.5. The vector is network-accessible, low complexity, no privileges, and no user interaction. It maps to CWE-400, indicating uncontrolled resource consumption. Published impact is availability only; confidentiality and integrity impacts are not indicated.

Likely exposure

Exposure is most relevant to affected Windows client and server versions running or relying on Microsoft Message Queuing. Risk increases where MSMQ is reachable over a network, especially from less trusted segments. The provided sources do not confirm whether MSMQ must be enabled by default.

Exploitation context

The source bundle does not indicate active exploitation, and CISA KEV status is false. The CVSS exploit maturity value is unproven. Treat this as a credible denial-of-service risk because it is unauthenticated and network-accessible, but do not assume known in-the-wild exploitation from the provided evidence.

Researcher notes

Evidence is limited to the CVE record, Microsoft advisory, CVSS, CWE, affected product list, and KEV=false status. No exploit details, proof-of-concept, or in-the-wild exploitation are provided. Avoid assuming affected configurations beyond Microsoft’s listed Windows versions and MSMQ context.

Mitigation direction

  • Apply Microsoft’s official update or guidance for CVE-2025-21290.
  • Prioritize internet-facing or cross-segment systems using MSMQ.
  • Limit MSMQ network reachability to required trusted systems.
  • Review business applications that depend on MSMQ availability.
  • Monitor vendor guidance for any revised mitigations or affected versions.

Validation and detection

  • Inventory Windows systems listed as affected by Microsoft.
  • Identify systems where MSMQ is installed, enabled, or business-critical.
  • Check patch compliance against Microsoft’s CVE-2025-21290 advisory.
  • Confirm MSMQ is not reachable from unnecessary network segments.
  • Review monitoring for MSMQ availability or resource-exhaustion symptoms.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-21290 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C3.93.6microsoft

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-21290Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows 10 Version 150710.0.10240.0Listed
MicrosoftWindows 10 Version 160710.0.14393.0Listed
MicrosoftWindows 10 Version 180910.0.17763.0Listed
MicrosoftWindows 10 Version 21H210.0.19044.0Listed
MicrosoftWindows 10 Version 22H210.0.19045.0Listed
MicrosoftWindows 11 version 22H210.0.22621.0Listed
MicrosoftWindows 11 version 22H310.0.22631.0Listed
MicrosoftWindows 11 Version 23H210.0.22631.0Listed
MicrosoftWindows 11 Version 24H210.0.26100.0Listed
MicrosoftWindows Server 2008 R2 Service Pack 16.1.7601.0Listed
MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)6.1.7601.0Listed
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0Listed
MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)6.0.6003.0Listed
MicrosoftWindows Server 20126.2.9200.0Listed
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0Listed
MicrosoftWindows Server 2012 R26.3.9600.0Listed
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0Listed
MicrosoftWindows Server 202210.0.20348.0Listed
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0Listed
MicrosoftWindows Server 202510.0.26100.0Listed
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.