Skip to content
Server Security Center
KEVcritical9.4

CVE-2025-54948: Trend Micro Apex One OS Command Injection

Trend Micro Apex One · listed in the CISA catalog of actively exploited vulnerabilities since 2025-08-18.

CVSS v3.1 (CVE record)
9.4
critical
EPSS (exploit probability, 30 days)
33%
higher than 98.3% of all CVEs
Added to CISA KEV
2025-08-18
US federal due date 2025-09-08
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2025-54948 explained

CVE-2025-54948 is an OS command injection vulnerability in the management console of Trend Micro Apex One (on-premise). A remote attacker without prior authentication could upload malicious code and run commands on affected installations. CISA lists it as known to be exploited, so unpatched servers face real risk.

Impact

An unauthenticated attacker with network access to the management console can execute commands on the Apex One server. No user interaction is needed. This can lead to high loss of confidentiality and availability and some loss of integrity. CISA rates it automatable, meaning attackers can exploit it at scale, with total technical impact, meaning full control of the affected component. Attackers are known to use it.

Who is affected

Trend Micro Apex One (on-premise) is affected from version 2019 (14.0) up to but not including 14.0.0.14039, as published in the CVE record by Trend Micro. The fix is in 14.0.0.14039. Administrators running any earlier build of the 2019 (14.0) line should treat their servers as vulnerable.

Written with AI from the data on this page and checked against it automatically.

Official 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.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Trend Micro, Inc. Trend Micro Apex One
    Affected
    • ≥ 2019 (14.0), < 14.0.0.14039
    Fixed in
    • 14.0.0.14039

How to fix it

What to do

  1. Update Trend Micro Apex One (on-premise) to 14.0.0.14039 or later.
  2. Follow the Trend Micro advisory and apply any mitigations it describes, as CISA's required action directs.
  3. Restrict network access to the Apex One management console and keep it off the internet.
  4. Check Apex One servers for signs of compromise, such as unexpected uploaded files or commands.
  5. If mitigations cannot be applied, follow CISA's guidance to discontinue use of the product.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-78 OS Command Injection

Questions about CVE-2025-54948

Is CVE-2025-54948 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-08-18, with a due date of 2025-09-08 for US federal agencies. Whether it is used in ransomware campaigns is unknown.
Does an attacker need credentials?
No. The description states a pre-authenticated remote attacker can exploit it, and the CVSS vector shows no privileges and no user interaction are required. Network access to the management console is enough.
Which version fixes the issue?
The CVE record names 14.0.0.14039 as the fixed version of Trend Micro Apex One. Earlier builds starting from 2019 (14.0) are affected.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.