Skip to main content
Mallory
CriticalVulnerability

CVE-2025-49220: Pre-authentication RCE in Trend Micro Apex Central ConvertFromJson

Published Jun 17, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS2.2%83rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Trend Micro
IdentifiersCVE-2025-49220CWE-502 · Deserialization of Untrusted Data

CVE-2025-49220 is a critical insecure deserialization vulnerability in Trend Micro Apex Central affecting versions below 8.0.7007. The flaw is associated with improper validation of user-supplied input in the ConvertFromJson method. A remote attacker can send specially crafted input that is deserialized by the application, resulting in execution of attacker-controlled code before authentication. The issue is distinct from CVE-2025-49219 but is described as similar in nature, differing by the affected method.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can lead to pre-authentication remote code execution on the affected Apex Central server. Because exploitation does not require prior authentication, an external attacker may be able to fully compromise the application host, execute arbitrary commands or payloads in the server context, and use that access as a foothold for broader compromise of connected management infrastructure.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of Apex Central management interfaces to untrusted networks, restrict access to trusted administrative hosts or network segments, and monitor for anomalous requests targeting application deserialization paths. Temporary mitigation should be treated only as a short-term risk reduction measure because the vulnerability is remotely reachable and does not require authentication.

Remediation

Patch, then assume compromise.

Upgrade Trend Micro Apex Central to version 8.0.7007 or later. For Apex Central on-premises 2019 deployments, apply patch CP B7007. For Apex Central as a Service, update to at least the April 2025 Monthly Release. Vendor-provided security updates should be applied urgently due to the critical severity and pre-authentication attack surface.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Trend MicroApex Centralapplication
FAQ

Frequently asked questions

Is CVE-2025-49220 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-49220 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-49220?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-49220.
Is there a patch for CVE-2025-49220?
Upgrade Trend Micro Apex Central to version 8.0.7007 or later. For Apex Central on-premises 2019 deployments, apply patch CP B7007.
What products are affected by CVE-2025-49220?
Trend Micro Apex Central.
How severe is CVE-2025-49220?
CVE-2025-49220 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 2.2% (83rd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.