CVE-2025-54948 — Apexone Server
CRITICALCVE-2025-54948 is a critical-severity (CVSS 9.4) OS Command Injection vulnerability in trendmicro apexone server. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-08-18) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.
A vulnerability in Trend Micro Apex One (on-premise) management console could allow a pre-authenticated remote attacker to upload malicious code and execute commands on affected installations.
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-08-18. Federal agencies were required to remediate by 2025-09-08.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-54948.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2025-54948 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Description
A vulnerability in Trend Micro Apex One (on-premise) management console could allow a pre-authenticated remote attacker to upload malicious code and execute commands on affected installations.
Affected Products
apexone servertrendmicroDetection & mitigation playbook
Vendor / applianceDetect
Inventory every trendmicro apexone server deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2025-54948 yet — track the trendmicro apexone server advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2025-54948 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.