← ← Back to all products
All badges & lifecycle API →
VMware Cloud FoundationEnd of Life (EOL) Dates & Support Status
Active
Cloud & PlatformsLatest Version: 9.1.1.0Latest Release: Sep 3, 2026
VMware Cloud Foundation is an integrated cloud infrastructure platform for private and hybrid clouds.
Support summary
VMware Cloud Foundation currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
Jun 1, 2027
VMware Cloud Foundation 5.1 · 247 days left
Supported cycles
5
0 lts
Versions
16
Latest Version
9.1.1.0
Active Support
5
EOL
11
Lifecycle Timeline
Feb 4, 2021As of Sep 27, 2026
9.1Active · Aug 12, 2028
9.0Active · Sep 17, 2027
5.2Active · Oct 11, 2027
5.1Active · Jun 1, 2027
5.0Active · Jun 1, 2027
4.5EOL · May 31, 2025
3.11EOL · Apr 30, 2023
4.4EOL · Sep 30, 2024
4.3EOL · Oct 31, 2023
4.2EOL · May 25, 2021
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 9.1 | May 12, 2026 | Maintained | Aug 12, 2028 | 9.1.1.0 | No | Active |
| 9.0 | Jun 17, 2025 | Maintained | Sep 17, 2027 | 9.0.2.0 | No | Active |
| 5.2 | Jul 23, 2024 | Maintained | Oct 11, 2027 | 5.2.3 | No | Active |
| 5.1 | Nov 7, 2023 | Maintained | Jun 1, 2027 | 5.1.1 | No | Active |
| 5.0 | Jun 1, 2023 | Maintained | Jun 1, 2027 | 5.0.0.1 | No | Active |
| 4.5 | Oct 11, 2022 | Ended | May 31, 2025 | 4.5.2 | No | EOL |
| 3.11 | Feb 14, 2022 | Ended | Apr 30, 2023 | 3.11.0.1 | No | EOL |
| 4.4 | Feb 10, 2022 | Ended | Sep 30, 2024 | 4.4.1 | No | EOL |
| 4.3 | Aug 24, 2021 | Ended | Oct 31, 2023 | 4.3.1 | No | EOL |
| 4.2 | Feb 4, 2021 | Ended | May 25, 2021 | 4.2.1 | No | EOL |
| 4.1 | Oct 6, 2020 | Ended | Feb 10, 2022 | 4.1.0 | No | EOL |
| 3.10 | May 26, 2020 | Ended | Sep 1, 2022 | 3.10.2 | No | EOL |
| 4.0 | Apr 14, 2020 | Ended | Aug 24, 2021 | 4.0.1 | No | EOL |
| 3.9 | Oct 24, 2019 | Ended | Oct 24, 2020 | 3.9.1 | No | EOL |
| 3.8 | Jul 18, 2019 | Ended | Jul 18, 2020 | 3.8.1 | No | EOL |
| 2.3 | Aug 15, 2018 | Ended | Nov 15, 2020 | 2.3.2 | No | EOL |
Data sources
Embed this badge
Show VMware Cloud Foundation's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/vmware-cloud-foundation/)HTML
<a href="https://eol.wiki/vmware-cloud-foundation/"><img src="https://eol.wiki/badge/vmware-cloud-foundation.svg" alt="VMware Cloud Foundation end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of VMware Cloud Foundation have reached end of life?
The following VMware Cloud Foundation versions have reached end of life and no longer receive security updates: 4.5, 3.11, 4.4, 4.3, 4.2, 4.1, 3.10, 4.0 (and 3 more). It is recommended to upgrade to a supported version.
Is it safe to continue using VMware Cloud Foundation 4.5?
VMware Cloud Foundation 4.5 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of VMware Cloud Foundation?
The latest version of VMware Cloud Foundation is 9.1.1.0, released in the 9.1 release cycle.
How many versions of VMware Cloud Foundation are currently supported?
VMware Cloud Foundation currently has 5 actively supported version(s): 9.1, 9.0, 5.2, 5.1, 5.0.
When does VMware Cloud Foundation 9.1 reach end of life?
VMware Cloud Foundation 9.1 is scheduled to reach end of life on Aug 12, 2028.
What should I do when VMware Cloud Foundation reaches end of life?
When a VMware Cloud Foundation version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.