Trend Micro TrendAI Apex One/TrendAI Apex One as a Service origin validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Trend Micro TrendAI Apex One and TrendAI Apex One as a Service. It has been declared as critical. This issue affects some unknown processing. The manipulation results in origin validation. This vulnerability was named CVE-2026-45207. The attack needs to be approached locally. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Trend Micro TrendAI Apex One and TrendAI Apex One as a Service (version now known). It has been classified as critical. Affected is some unknown processing. The manipulation with an unknown input leads to a origin validation vulnerability. CWE is classifying the issue as CWE-346. The product does not properly verify that the source of data or communication is valid. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
An origin validation vulnerability in the Apex One/SEP agent could allow a local attacker to escalate privileges on affected installations. This is similar to CVE-2026-45206 but exists in a different process protection communication mechanism. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.
The advisory is shared for download at success.trendmicro.com. This vulnerability is traded as CVE-2026-45207 since 05/11/2026. The exploitability is told to be easy. The attack needs to be approached locally. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 05/24/2026).
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at EUVD (EUVD-2026-31279) and CERT Bund (WID-SEC-2026-1643). Once again VulDB remains the best source for vulnerability data.
Affected
- Trend Micro Apex One
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.trendmicro.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (trendmicro): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Origin validationCWE: CWE-346 / CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
05/11/2026 CVE reserved05/21/2026 Advisory disclosed
05/21/2026 VulDB entry created
05/24/2026 VulDB entry last update
Sources
Vendor: trendmicro.comAdvisory: success.trendmicro.com
Status: Confirmed
CVE: CVE-2026-45207 (🔒)
GCVE (CVE): GCVE-0-2026-45207
GCVE (VulDB): GCVE-100-365028
EUVD: 🔒
CERT Bund: WID-SEC-2026-1643 - Trend Micro Apex One: Mehrere Schwachstellen ermöglichen Privilegieneskalation und die Ausführung von Code
Entry
Created: 05/21/2026 16:41Updated: 05/24/2026 06:02
Changes: 05/21/2026 16:41 (61), 05/21/2026 19:58 (1), 05/24/2026 06:02 (7)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.