CVE-2025-49212 is a critical insecure deserialization vulnerability in Trend Micro Endpoint Encryption PolicyServer. The flaw is associated with missing input validation in the PolicyValueTableSerializationBinder class, allowing attacker-controlled serialized input to be processed unsafely. A remote, unauthenticated attacker can send specially crafted input that triggers deserialization of malicious data and results in code execution before authentication. The issue is described as similar to CVE-2025-49220, but occurring in a different method within the affected product.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Trend Micro Endpoint Encryption (TMEE) PolicyServer pre-auth remote code execution vector caused by insecure deserialization.
Critical remote code execution vulnerability in Trend Micro Endpoint Encryption PolicyServer caused by improper input validation in PolicyValueTableSerializationBinder leading to unsafe deserialization.
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.