VMware Aria Automation 8.18 · Version Status

VMware Aria Automation 8.18 End of Life Date

VMware Aria Automation 8.18 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (support.broadcom.com); the source of each date is on the product page.

✓ VMware Aria Automation 8.18 is actively supported. EOL date: October 11, 2027.
📅 Get reminded before VMware Aria Automation 8.18 reaches EOL on October 11, 2027 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Oct 11, 2027
365 days remaining
Latest Release
8.18.1
Standard release
Release Date
Jul 24, 2024
VMware Aria Automation 8.18 series
Lifecycle detail

VMware Aria Automation 8.18 was released on July 24, 2024 and support is scheduled to end on October 11, 2027 — a planned supported lifespan of 3 years and 3 months, longer than the 1 year and 2 months median for VMware Aria Automation releases.

← VMware Aria Automation 8.13 All VMware Aria Automation versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All VMware Aria Automation Versions
VersionLatestEOL DateStatus
8.2 (vRealize Automation) 8.2.0 Oct 31, 2022 EOL
8.3 (vRealize Automation) 8.3.0 Oct 31, 2022 EOL
8.4 (vRealize Automation) 8.4.2 Oct 31, 2022 EOL
8.5 (vRealize Automation) 8.5.1 Oct 31, 2022 EOL
8.6 (vRealize Automation) 8.6.2 Jan 18, 2023 EOL
8.7 (vRealize Automation) 8.7.0 Mar 22, 2023 EOL
8.8 (vRealize Automation) 8.8.2 Jul 12, 2023 EOL
8.9 (vRealize Automation) 8.9.1 Sep 6, 2023 EOL

What does VMware Aria Automation 8.18 end of life mean?

When VMware Aria Automation 8.18 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running VMware Aria Automation 8.18 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to VMware Aria Automation 8.18 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does VMware Aria Automation 8.18 reach end of life?
VMware Aria Automation 8.18 reaches end of life on October 11, 2027. That is 365 days remaining.
Is VMware Aria Automation 8.18 still supported?
Yes, VMware Aria Automation 8.18 is currently supported. The EOL date is October 11, 2027.
What should I upgrade to from VMware Aria Automation 8.18?
The recommended upgrade from VMware Aria Automation 8.18 is VMware Aria Automation 8.18 — the latest actively supported version. Check the VMware Aria Automation full timeline for all supported versions.
What are the security risks of running VMware Aria Automation 8.18 past EOL?
When VMware Aria Automation 8.18 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL VMware Aria Automation should migrate immediately or implement compensating controls.
Data from the vendor's own lifecycle pages (support.broadcom.com) · Generated at build time · How we source data →