Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Windows Message Queuing mqac.sys Double Free Local Privilege Escalation

IdentifiersCVE-2026-33838CWE-415· Double Free

CVE-2026-33838 is a local elevation-of-privilege vulnerability in Microsoft Windows Message Queuing (MSMQ). The flaw is a double free condition in the mqac.sys driver. According to the provided context, the issue stems from failure to validate the existence of an object before performing additional free operations on that object, resulting in a double free. An attacker with the ability to run code locally with low privileges can exploit the flaw without user interaction. Successful exploitation can lead to arbitrary code execution in kernel context and elevation to SYSTEM.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a local authorized attacker to elevate privileges from a low-privileged context to SYSTEM. Because exploitation may yield arbitrary code execution in the Windows kernel, the impact spans high confidentiality, integrity, and availability consequences on the affected host. This can enable full compromise of the local system, including tampering with protected resources, disabling security controls, and destabilizing or crashing the system.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting local code execution opportunities for untrusted users, restricting access to affected systems, and disabling or removing Windows Message Queueing where it is not required. Harden endpoints to prevent low-privileged code execution, and monitor for suspicious local privilege escalation activity involving MSMQ or the mqac.sys driver. These are interim measures only; the official Microsoft update is the definitive mitigation.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update that addresses CVE-2026-33838. The provided context states that Microsoft issued an official fix and update for the vulnerability through the MSRC Security Update Guide. Prioritize patching Windows systems that have Message Queueing enabled or installed.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows Message Queuingoperating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.