CVE-2025-30678: Trend Micro Apex Central · SSRF
Affects Trend Micro Apex CentralSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Trend Micro, Inc. Trend Micro Apex Central | Affected
| Fixed in– |
AI-suggested
Apply vendor-provided patches immediately once available. Since no patches are currently published, monitor Trend Micro advisories closely for updates addressing CVE-2025-30678.
Implement strict network segmentation to limit the Apex Central server’s access to sensitive internal resources and cloud metadata endpoints, reducing the potential impact of SSRF exploitation.
Use web application firewalls (WAFs) or intrusion prevention systems (IPS) with rules tuned to detect and block SSRF attack patterns targeting the modTMSM component.
Restrict and monitor outbound HTTP/HTTPS requests from the Apex Central server to only necessary destinations, employing egress filtering to prevent unauthorized internal or external requests.
Educate users and administrators about the risk of social engineering or phishing that could trigger the SSRF vulnerability, emphasizing caution with unexpected links or requests related to Apex Central.
Enable detailed logging and monitoring on Apex Central to detect unusual request patterns or anomalies indicative of SSRF attempts.
Consider deploying virtual patching or temporary compensating controls if immediate patching is not feasible, such as disabling or restricting vulnerable functionality if possible.
Review and harden configuration parameters related to modTMSM to ensure that parameters controlling server requests are validated and sanitized to the extent configurable.
Description
A Server-side Request Forgery (SSRF) vulnerability in Trend Micro Apex Central (on-premise) modTMSM component could allow an attacker to manipulate certain parameters leading to information disclosure on affected installations.