CVE-2026-109459 · Infrastructure
NO FIX YET
A heap-based buffer overflow in the Windows Message Queuing Queue Manager lets an attacker write past allocated memory. The flaw can be triggered over the network and allows code execution without authentication.
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 servers and workstations with the Message Queuing feature installed and its Queue Manager reachable from the network are the exposed systems. The sources do not say which Windows builds are affected or whether the feature is on by default, so teams should confirm that before deciding whether they can skip it.
Not affected if msmq-not-installed
Who cares msmq, windows
No fix yet, per the sources.
Heap-based buffer overflow 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.