VMware Cloud Foundation 4.5 EOL May 2025 – What Works

What End of Life Means for VMware Cloud Foundation 4.5

On May 31, 2025, VMware Cloud Foundation 4.5 reached end of life (EOL), with active support ending on the same date. This release is not an LTS (Long Term Support) build, and the latest version available in the 4.5 line is 4.5.2. For organizations still running this version, understanding the practical consequences of EOL is essential for planning and risk management.

What Stops Working After EOL

After the EOL date, Broadcom (the current owner of VMware products) stops delivering:

• Security patches – No new fixes for vulnerabilities discovered after May 31, 2025.
• Bug fixes – Any software defects found in Cloud Foundation 4.5 will not be addressed.
• Technical support – Vendor-provided assistance, including troubleshooting and break-fix, is no longer available.

What Keeps Working

Existing functionality remains intact. The software does not stop operating, and any components that were already licensed continue to run. However, without vendor updates, the environment becomes static. New workloads can still be deployed, but any reliance on the 4.5 baseline means accepting the known state of the software at the time of EOL.

Real Risks of Running Unsupported Cloud Foundation 4.5

Operating any enterprise infrastructure software past its vendor support window introduces several categories of risk:

• Security exposure – Unpatched vulnerabilities are a primary concern. Without a vendor-provided security fix, a flaw discovered in the SDDC stack (vSphere, vSAN, NSX, or SDDC Manager) may be actively exploited.
• Compliance gaps – Regulatory frameworks (PCI DSS, SOC 2, HIPAA) often require that all software in scope be under vendor support or have a documented compensating control. Running an unsupported version can trigger audit findings.
• Integration degradation – Third-party tools that validate compatibility against Cloud Foundation versions may drop support for 4.5, leading to broken integrations or inability to onboard new tools.
• No escalation path – If a critical issue arises, there is no vendor to escalate to. Recovery depends entirely on internal expertise and community knowledge.

Who Legitimately Stays on Cloud Foundation 4.5

Despite the risks, several scenarios may keep an organization on 4.5 for a period after EOL:

• Stable, unchanging workloads – If the environment is a fixed-capacity deployment with no plans to add new hardware or software, and the current functionality is sufficient, delaying migration can be a calculated risk.
• Application dependency locks – Some software may be certified only against a specific SDDC version. Moving to a newer Cloud Foundation release could require recertification of business-critical applications.
• Hardware constraints – The underlying hardware may not meet the requirements for the next Cloud Foundation version (e.g., firmware, driver support, or CPU compatibility).
• Budget cycles – A migration project may be planned but not yet funded. Keeping the existing environment running while procurement is arranged is a transitional reality.

Third-Party Support: A Viable Option for Extended Life

For organizations that cannot migrate immediately—or that choose not to for legitimate operational reasons—third-party support from providers like 3rd Party Support can bridge the gap. This service typically covers:

• Security patch management – Backported critical patches for the specific version, based on vulnerability analysis.
• Bug fixes – Hotfixes for software defects that are not available from the vendor.
• Technical support – Direct access to engineers experienced with Cloud Foundation 4.5, providing break-fix assistance and troubleshooting.

Pricing for third-party support is often a fraction of the last vendor renewal, making it an economical choice for maintenance-only environments. The support contract runs independently of the vendor’s lifecycle, so organizations can stay on 4.5 for as long as they need while maintaining a defensible support posture.

Next Steps for Your Environment

If you are still running VMware Cloud Foundation 4.5, the first step is to inventory your current deployment and assess whether a migration to a newer version (such as 4.5.2, the latest in the 4.5 line) is feasible. If migration is not practical, arranging third-party support ensures that your environment remains covered for security and operational issues.

To discuss your specific situation or get a quote for continuing support, contact our team.