CVE-2025-71210 — Path Traversal in Trend Micro, Inc. Apex One
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. 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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 3.8% (30-day exploitation probability)+13
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Trend Micro, Inc. Apex One, Trend Micro, Inc. TrendAI Apex One, Trend Micro, Inc. TrendAI Apex One as a Service).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Trend Micro, Inc. | Apex One | < 14.0.0.14136< 14.0.20315 | Vulnerable | NIST National Vulnerability Database |
| Trend Micro, Inc. | TrendAI Apex One | ≥ 2019 (14.0) and < 14.0.0.14136 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Trend Micro, Inc. | TrendAI Apex One as a Service | ≥ SaaS and < 14.0.20315 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | security@trendmicro.com via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | trendmicro via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: security@trendmicro.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 3.81%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor file creation in web directories and paths with traversal sequences (../).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · trend micro, inc./trendai apex one, trend micro, inc./trendai apex one as a service
- SSVC assessment updated
- Record published
- CVSS changed · 9.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-45208 TOCTOU Race Condition in Trend Micro, Inc. Apex One May 21, 2026
- High CVE-2026-45207 An origin validation vulnerability in the Apex One/SEP agent could allow a local… May 21, 2026
- High CVE-2026-45206 An origin validation vulnerability in the Apex One/SEP agent could allow a local… May 21, 2026
- High CVE-2026-34929 An origin validation vulnerability in the Apex One/SEP agent could allow a local… May 21, 2026
- High CVE-2026-34927 An origin validation vulnerability in the Apex One/SEP agent could allow a local… May 21, 2026
- High CVE-2026-34928 An origin validation vulnerability in the Apex One/SEP agent could allow a local… May 21, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-71210 is "Path Traversal in Trend Micro, Inc. Apex One", rated Critical. It affects Apex One (Trend Micro, Inc.); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 3.81% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.