Quick answers
- Is CVE-2026-45207 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45207 being exploited in the wild.
- How severe is CVE-2026-45207?
- High severity, with a CVSS score of 7.8, published 21 May 2026.
- Which products and versions are affected?
- Trend Micro Apex One as a Service Agent Builds below 14.0.20731.
- Is there a fix for CVE-2026-45207?
- A patch was published on 2026-05-21. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45207 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-45207?
- Check whether you run Trend Micro Apex One Agent, Trend Micro Apex One as a Service Agent or Trend Micro Vision One Endpoint Security - Standard Endpoint Protection Agent at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An origin validation error (CWE-346) exists within the process protection communication mechanism of the Trend Micro Apex One and Vision One Standard Endpoint Protection (SEP) agents. The vulnerability stems from insufficient verification of the source of inter-process communications. A local attacker with low-privileged code execution capabilities can exploit this flaw to bypass security controls and escalate their privileges to a higher level. This specific issue is part of a series of similar vulnerabilities affecting different communication channels, such as named pipes and other IPC mechanisms. Patches are available in Apex One (on-prem) Agent build 17079 and SaaS Agent build 14.0.20731.
Affected products
- Trend Micro Apex One (On-prem) Agent Builds below 17079
- Trend Micro Apex One as a Service Agent Builds below 14.0.20731
- Trend Micro Vision One Endpoint Security - Standard Endpoint Protection (SEP) Agent Builds below 14.0.20731
Timeline
- 2026-05-21: disclosed
- 2026-05-21: advisory
- 2026-05-21: patched