CVE-2026-118126 · Infrastructure
NO FIX YET
A use-after-free bug in Windows Message Queuing lets an attacker who already has a local account raise their privileges. The sources give no more detail on the exact trigger.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Windows machines where the Message Queuing component is present and an authorized local user exists; the sources do not say which Windows versions or configurations are affected. Machines without Message Queuing installed are likely not exposed, but the sources do not confirm this. Single-user machines without untrusted local accounts carry less risk.
Not affected if msmq-not-installed
Who cares msmq, windows
No fix yet, per the sources.
Use after free in Windows Message Queuing allows an authorized attacker to elevate privileges locally.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.