CVE-2026-50694 is a high-severity remote code execution vulnerability in Windows Secure Socket Tunneling Protocol (SSTP). The flaw is a use-after-free condition in the SSTP implementation that can be triggered remotely against an SSTP server. By sending a specially crafted malicious SSTP packet, an unauthenticated attacker can cause the server to access memory after it has been freed, creating a path to arbitrary code execution in the context of the vulnerable service. The issue affects multiple supported Windows client and server releases, including Server Core installations of several Windows Server versions.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical remote code execution vulnerability in Windows Secure Socket Tunneling Protocol.
A high-severity use-after-free remote code execution vulnerability in Windows Secure Socket Tunneling Protocol (SSTP) that allows an unauthorized attacker to execute code over a network.
A critical remote code execution vulnerability in Windows Secure Socket Tunneling Protocol (SSTP).
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.