TrendAI Apex One: Improper Limitation of a Pathname to a Restricted Directory
CVE-2025-71211 is a critical-severity improper limitation of a pathname to a restricted directory vulnerability in TrendAI Apex One from Trend Micro, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 14.0.0.14136 as the first without the flaw, so updating TrendAI Apex One to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 3.75% chance of exploitation within 30 days, which is in the top 9.94% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update TrendAI Apex One to 14.0.0.14136 or a later version.
- Update TrendAI Apex One as a Service to 14.0.20315 or a later version.
- Update Apex One to 14.0.0.14136 or 14.0.20315, whichever matches your release line, or a later version.
- Read the advisory on success.trendmicro.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Trend Micro | TrendAI Apex One | 2019 (14.0) up to, but not including, 14.0.0.14136 | 14.0.0.14136 |
| Trend Micro | TrendAI Apex One as a Service | SaaS up to, but not including, 14.0.20315 | 14.0.20315 |
| Trend Micro | Apex One | before 14.0.0.14136; before 14.0.20315 | 14.0.0.14136, 14.0.20315 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (trendmicro.com).
Official description
A vulnerability in the Trend Micro Apex One management console could allow a remote attacker to upload malicious code and execute commands on affected installations. This vulnerability is similar in scope to CVE-2025-71210 but affects a different executable. Please note: although this vulnerability carries a technical critical CVSS rating, this was reported via responsible disclosure via a researcher through the Zero Day Initiative. The SaaS versions of the product have already been mitigated and no customer action required. For this particular vulnerability, an attacker must have access to the Trend Micro Apex One Management Console, so customers that have their console�s IP address exposed externally should consider mitigating factors such as source restrictions if not already applied.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- zerodayinitiative.com/advisories/ZDI-26-137/Third Party Advisory
Other vulnerabilities in TrendAI Apex One
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 9.8 Critical severity
- 9.9 Critical severity
- 7.6 High severity
- 9.4 Critical severity
- 9.4 Critical severity
- 9.4 Critical severity
Spotted an error? Tell us.