Trend Micro Apex One End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Trend Micro Apex One versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Trend Micro Apex One Apex One as a Service is supported until December 31, 2027, its end-of-support date. It is also the next Trend Micro Apex One version to reach end of life. 1 of 3 tracked Trend Micro Apex One versions is past end of life; the most recent to reach it, OfficeScan XG / XG SP1 (predecessor), did so on March 31, 2021. The full Trend Micro Apex One lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| OfficeScan XG / XG SP1 (predecessor) | — | — | Mar 31, 2021 | 2020 days past EOL | EOL |
| Apex One as a Service | — | — | Dec 31, 2027 | 446 days remaining | Active |
| Apex One 2019 (on-premises) | — | — | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/trend-micro-apex-one)
Trend Micro Apex One lifecycle status — the real story
Trend Micro Apex One is the endpoint protection platform that succeeded OfficeScan; it ships as an on-premises server (the Apex One 2019 release, kept current through service packs and patches) and as Apex One as a Service. Trend Micro's Supported and End-of-Life Products and Services list (updated October 5, 2026) carries the on-premises Apex One as supported with no End-of-Sale or End-of-Life date announced, and Apex One as a Service with End-of-Sale on December 31, 2025 and End-of-Life on December 31, 2027. The predecessor OfficeScan XG and XG SP1 reached End-of-Life on March 31, 2021: "Trend Micro will no longer develop hot fixes or patches for this version." For the on-premises product the operative lifecycle is per build: "Trend Micro will provide support for program builds 18 months after the month it is released" (Apex One Support Policy, in force since December 1, 2022), with regular patch releases twice a year.
Apex One and OfficeScan carry eleven entries in CISA's Known Exploited Vulnerabilities catalog (2026.10.08): CVE-2026-34926 (filed as 'Apex One', added May 21, 2026), CVE-2025-54948 ('Apex One', August 18, 2025), CVE-2023-41179 ('Apex One and Worry-Free Business Security', September 21, 2023), CVE-2022-40139 ('Apex One and Apex One as a Service', September 15, 2022), CVE-2021-36741 and CVE-2021-36742 ('Apex One, Apex One as a Service, and Worry-Free Business Security'), CVE-2020-8467 and CVE-2020-8599 ('Apex One and OfficeScan'), CVE-2020-8468 and CVE-2020-24557 (joint Apex One, OfficeScan and Worry-Free strings), all added November 3, 2021, and CVE-2019-18187 (filed as 'OfficeScan', added November 3, 2021, joined by a force override; NVD names OfficeScan 11.0 SP1 and XG). None is flagged as used in ransomware campaigns. The Apex Central console has its own entry and its own page.
Field mapping: eol is Trend Micro's 'End-of-Life' day, defined on the list as "the date when maintenance for a product and service is no longer available", exactly as printed (Apex One as a Service: December 31, 2027; OfficeScan XG: March 31, 2021); the on-premises line has no printed date and is served as supported. 'End-of-Sale' is carried as a vendor field, not as a support milestone. releaseDate is null because the vendor pages print no general-availability day. The success.trendmicro.com articles are readable without a browser and are checked automatically.
Trend Micro Apex One release and support pattern
Of the 3 release lines tracked, 1 is past end of life and 2 are still within support. The next scheduled end of life is saas on December 31, 2027 — 446 days from this build.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Trend Micro Apex One security intelligence
CISA KEV history: Trend Micro Apex One is named in CISA's Known Exploited Vulnerabilities catalog 11 times, most recently on 2026-05-21. Derived from CISA's live catalog at every build.
What does Trend Micro Apex One end of life mean for your organization?
When a version of Trend Micro Apex One reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Trend Micro Apex One should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Trend Micro Apex One reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Trend Micro Apex One versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Trend Micro Apex One has 1 version past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Trend Micro Apex One is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."