Loading vulnerability…
A remote code execution vulnerability affecting Windows Telephony Server. The available information identifies the issue as an RCE flaw in the Windows Telephony Server component and lists it among Microsoft’s February 2025 security updates. No further technical details about the root cause, vulnerable function, attack vector, or exploitation mechanics are currently available.
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.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity Windows Telephony Server remote code execution vulnerability with CVSS 8.8.
A high-severity remote code execution vulnerability in Windows Telephony Service mentioned in the broader list of February 2025 Microsoft vulnerabilities.
A remote code execution vulnerability in Windows Telephony Server.
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.