Skip to main content
VulnerabilityPublished

CVE-2025-71216: Trend Micro TrendAI Apex One (Mac) · CWE-367

Affects Trend Micro TrendAI Apex One (Mac)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Trend Micro, Inc.TrendAI Apex One (Mac)Affected
  • ≥ NA, < NA
Fixed in–

AI-suggested

The vulnerability has been addressed by Trend Micro through ActiveUpdate and SaaS updates released in mid to late 2025 (SaaS 2507 and 2005 Yearly Release). Users should ensure their Trend Micro Apex One (Mac) installations are fully updated to these or later versions. No additional mitigation actions are required beyond applying these official updates.

Description

A time-of-check time-of-use vulnerability in the Trend Micro Apex One (mac) agent cache mechanism could allow a local attacker to escalate privileges on affected installations. 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 following information is provided as informational only for CVE references, as these were addressed already via ActiveUpdate/SaaS updates in mid to late 2025 (SaaS 2507 & 2005 Yearly Release).

References

Community reviews

Loading reviews…