Skip to content
major vulnerability· requires attention

Affects widely deployed Trend Micro Apex Central; unauthenticated DoS could disrupt security operations across enterprises.

Web

CVE-2025-69260

9.8
Critical
EPSS 2%Patch availableJan 11, 2026

Unauthenticated out-of-bounds read in Apex Central allows DoS.

common questions

Is CVE-2025-69260 being exploited?

Not confirmed. CVE-2025-69260 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.6% probability of exploitation in the next 30 days.

How severe is CVE-2025-69260?

CVE-2025-69260 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-69260?

Yes. A fix has been recorded for CVE-2025-69260. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-69260 affect?

CVE-2025-69260 affects Trend Micro Apex Central. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-69260?

Apply vendor patch/upgrade to fixed version

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Trend Micro Apex Central
impact

Unauthenticated remote DoS via out-of-bounds read; attacker can crash the Apex Central service, impacting availability.

action required

Immediate action required

affected versions
Trend Micro, Inc. Trend Micro Apex Central
  • affected>= 2019 (14.0) and < Build 7190

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free