LiveActive security incident?Get immediate response
CVE Record

CVE-2026-54992: Microsoft Message Queuing Queue Manager Remote Code Execution Vulnerability

Heap-based buffer overflow in Windows Message Queuing Queue Manager allows an unauthorized attacker to execute code locally.

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A memory-safety flaw in Microsoft Message Queuing could let an unauthorized attacker run code on an affected Windows system. Successful exploitation could compromise data, alter the system, or interrupt operations. The supplied CVSS vector classifies the attack as local, so this is not documented here as a conventional remote, internet-facing attack.

Executive priority

Treat this as a high-priority patching item, particularly on critical servers using Message Queuing. The potential impact is complete system compromise, but the supplied evidence indicates a local attack vector and does not establish active exploitation. Track affected-host discovery and update completion to closure.

Technical view

CVE-2026-54992 is a CWE-122 heap-based buffer overflow in the Windows Message Queuing Queue Manager. It has CVSS 3.1 score 8.4: local access, low complexity, no privileges or user interaction, unchanged scope, and high confidentiality, integrity, and availability impact. The supplied evidence does not describe the vulnerable input or exploitation method.

Likely exposure

Exposure includes the listed Windows 10, Windows 11, and Windows Server releases where the vulnerable Message Queuing component is present. Prioritize systems running Message Queuing and accessible to untrusted local processes or users. The bundle provides base versions but no fixed builds, KB identifiers, or evidence of direct network exploitation.

Exploitation context

The supplied record is not marked as CISA KEV, and its CVSS temporal metric reports unproven exploitation. No cited evidence establishes active exploitation or public exploit availability. Exploitation is characterized as local, low-complexity, requiring neither privileges nor user interaction; the necessary local access mechanism is not explained.

Researcher notes

The record identifies a heap-based buffer overflow but provides no function, input path, trigger conditions, proof of concept, or fixed-version details. Researchers should avoid inferring network reachability from the title: the supplied CVSS vector is AV:L. Validate product applicability and remediation against Microsoft's advisory before drawing conclusions about reachable attack surfaces.

Mitigation direction

  • Review Microsoft's advisory and install the applicable security update for each affected Windows release.
  • Prioritize Message Queuing hosts supporting sensitive, privileged, or business-critical workloads.
  • Limit untrusted local access while updates are tested and deployed.
  • Check current Microsoft guidance for release-specific prerequisites or additional mitigations.

Validation and detection

  • Inventory listed Windows releases and record their exact edition, build, and servicing status.
  • Determine which systems have Microsoft Message Queuing installed or operational.
  • Use Microsoft's advisory to identify and verify the applicable installed security update.
  • Recheck Message Queuing-dependent applications after patching to confirm normal operation.
Prepared
Confidence
medium
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-122: 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-54992 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
8.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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: noTechnical Impact: total

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
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.55.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2026-54992Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 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 24H210.0.26100.0Listed
MicrosoftWindows 11 Version 25H210.0.26200.0Listed
MicrosoftWindows 11 version 26H110.0.28000.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 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-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.