CVE-2025-49213
Published: 17 June 2025
Summary
CVE-2025-49213 is a critical-severity Use of Obsolete Function (CWE-477) vulnerability in Trendmicro Trend Micro Endpoint Encryption. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 9.8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
An insecure deserialization vulnerability exists in the Trend Micro Endpoint Encryption PolicyServer. The flaw, tracked as CVE-2025-49213 and assigned CWE-502 along with CWE-477, permits pre-authentication remote code execution on affected installations and is similar to CVE-2025-49212 but resides in a separate method. It received a CVSS v3.1 base score of 9.8 reflecting network-accessible, unauthenticated attack conditions with high impact on confidentiality, integrity, and availability.
An unauthenticated remote attacker can send specially crafted serialized data to the PolicyServer over the network to execute arbitrary code without requiring credentials or user interaction. The current EPSS score of 0.0527 with a recorded peak of 0.0630 indicates limited observed exploitation interest to date.
Advisories from Trend Micro and the Zero Day Initiative are available at the referenced URLs for further details on affected versions and remediation steps.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-18647
Vulnerability details
An insecure deserialization operation in the Trend Micro Endpoint Encryption PolicyServer could lead to a pre-authentication remote code execution on affected installations. Note that this vulnerability is similar to CVE-2025-49212 but is in a different method.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing supplies malicious serialized objects, detecting unsafe deserialization and supporting corrective actions.
Institutionalized information sharing keeps developers aware of obsolete functions and the need to replace them with supported alternatives.
Regular reassessment flags use of obsolete functions whose security properties have degraded or whose replacements contain fixes for known weaknesses.
Evaluation of untrusted data handling (deserialization testing) reveals unsafe processing, which the required remediation process addresses.
Eliminates reliance on functions or components explicitly declared obsolete and unsupported by their maintainers.
Untrusted serialized data can be deserialized and observed inside the chamber, blocking gadget-chain exploitation outside the sandbox.
Validates or rejects untrusted serialized data before deserialization occurs.
Software and firmware updates replace obsolete functions whose retained presence leaves systems exposed to publicly known weaknesses.