CVE-2026-119967 · Infrastructure
NO FIX YET
Windows Message Queuing's Queue Manager has a use-after-free memory bug. A remote attacker with no account can send crafted network traffic to run code on the affected Windows machine.
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 with the Message Queuing (MSMQ) feature installed and reachable over the network are the ones to examine. The sources do not say which Windows versions or configurations are affected, or whether the feature is on by default. Systems without MSMQ installed are not exposed.
Not affected if msmq-not-installed
Who cares message-queuing, msmq, windows
Unknown from the sources. In the analyst’s queue.
No fix yet, per the sources.
Use after free in Windows Message Queuing Queue Manager allows an unauthorized attacker to execute code over a network.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/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.