Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2025-69258: Unauthenticated LoadLibraryEx RCE in Trend Micro Apex Central MsgReceiver.exe

Published Jan 8, 2026 · 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
EPSS3.6%90th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Trend Micro
IdentifiersCVE-2025-69258CWE-427

CVE-2025-69258 is a critical remote code execution vulnerability in Trend Micro Apex Central (on-premise) for Windows affecting versions prior to Build 7190. The flaw resides in the MsgReceiver.exe message-handling path, where a specially crafted network message can cause the service to pass attacker-controlled input to LoadLibraryExA and load an arbitrary DLL into the process. Reported technical details indicate that message ID 0x0a8d can supply the DLL name to a handler in msgHandlerLogReceiver.dll, resulting in attacker-controlled library loading into MsgReceiver.exe. Because the service runs with SYSTEM privileges, successful exploitation leads to execution of attacker-supplied code in that security context. The issue is remotely reachable, requires no authentication, and does not require user interaction.

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 allows an unauthenticated remote attacker to achieve arbitrary code execution on the Apex Central server with SYSTEM privileges. This gives the attacker full control of the affected host, including the ability to install malware, modify or destroy data, disable security controls, create privileged accounts, pivot further into the environment, and disrupt managed security operations dependent on the server.

Mitigation

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

If immediate patching is not possible, restrict network access to the Apex Central server and specifically to the MsgReceiver.exe service to trusted administrative networks and hosts only. Remove direct internet exposure, place the server behind appropriate segmentation such as a dedicated management VLAN or DMZ, allow only essential inbound connectivity, and monitor for unauthorized connection attempts or abnormal activity involving MsgReceiver.exe. These measures reduce exposure but do not eliminate the underlying vulnerability.

Remediation

Patch, then assume compromise.

Upgrade Trend Micro Apex Central (on-premise) for Windows to Critical Patch Build 7190 or later. Apply the vendor-provided security update across all affected installations and validate that the patched build is deployed successfully on every Apex Central server. Because public proof-of-concept exploit code is available and exploitation is low complexity, patching should be prioritized urgently.

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-69258 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-69258 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-69258?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2025-69258.
Is there a patch for CVE-2025-69258?
Upgrade Trend Micro Apex Central (on-premise) for Windows to Critical Patch Build 7190 or later. Apply the vendor-provided security update across all affected installations and validate that the patched build is deployed successfully on every Apex Central server.
What products are affected by CVE-2025-69258?
Trend Micro Apex Central.
How severe is CVE-2025-69258?
CVE-2025-69258 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 3.6% (90th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

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

View more in app →
+8 more in the timeline. Sign up to see them
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 activity34Community discussion across Reddit, Mastodon, and other social sources.