VMware Aria Operations End of Life (EOL) Dates & Support Timeline

VMware Aria Operations lifecycle status — the real story

VMware Aria Operations (vRealize Operations until 8.10, and vRealize Operations Manager before that) is VMware's monitoring and capacity platform, now sold inside VMware Cloud Foundation as VCF Operations. Its dates come from Broadcom's Product Lifecycle portal, which prints a General Availability and an End of Service date per build; "end of support" here is that End of Service, the same column the portal prints for vCenter and ESXi as their end of general support. Broadcom prints no End of Life (technical guidance) date for these builds.

Builds are grouped by minor line with the newest build as the latest. The 8.18 line, current since July 2024, ends with vSphere 8.0 in October 2027; 8.17 and 8.16 ended in October 2025, 8.14 and 8.12 at the end of 2024. One line, 8.1, has two builds with different end dates in Broadcom's table (8.1.0 October 2021, 8.1.1 July 2022); the later date is shown. Aria Operations for Logs and Aria Operations for Networks (vRealize Log Insight and Network Insight) are separate products.

CISA's Known Exploited Vulnerabilities catalog lists CVE-2026-22719 (VMware Aria Operations), CVE-2025-41244 (VMware Aria Operations and VMware Tools, a local privilege escalation through the service discovery feature) and CVE-2021-21975, filed as "vRealize Operations Manager API", this product's earlier name, and used in ransomware campaigns. The catalog's CVE-2023-20887 is filed as "Aria Operations for Networks" (formerly vRealize Network Insight), a different product, and is not counted here.

VMware Aria Operations release and support pattern

Across the 13 release lines with a published release date, VMware Aria Operations has shipped a new line roughly every 5 months (median interval). A line typically stays supported for about 2 years from its release to its end-of-life date (measured on the 13 lines with both dates published).

Of the 14 release lines tracked, 13 are past end of life and 1 is still within support. The newest line, 8.18, was released July 23, 2024. The next scheduled end of life is 8.18 on October 11, 2027 — 365 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.

VMware Aria Operations security intelligence

CISA KEV history: VMware Aria Operations is named in CISA's Known Exploited Vulnerabilities catalog 3 times, most recently on 2026-03-03, including use in ransomware campaigns. Derived from CISA's live catalog at every build.

What does VMware Aria Operations end of life mean for your organization?

When a version of VMware Aria Operations 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 VMware Aria Operations 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 VMware Aria Operations 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.

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 VMware Aria Operations versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products