EOL.Wiki EOL.Wiki
← ← Back to all products

VirtualBox

Active
Applications Latest Version: 7.2.6 Latest Release: Jan 30, 2026

Oracle VirtualBox is a free, open-source virtualization software for running multiple operating systems.

Versions

12

Latest Version

7.2.6

Active Support

2

EOL

10

Lifecycle Timeline

Today
7.2
7.2
7.1
7.1
7.0
7.0
6.1
6.1
6.0
6.0
5.2
5.2
5.1
5.1
5.0
5.0
4.3
4.3
4.2
4.2
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
7.2Aug 14, 2025-No7.2.6No
Active
7.1Sep 9, 2024-No7.1.16No
Active
7.0Oct 10, 2022-Mar 31, 20257.0.26No
EOL
6.1Dec 10, 2019-Jan 31, 20246.1.50No
EOL
6.0Dec 18, 2018-Jul 31, 20206.0.24No
EOL
5.2Oct 17, 2017-Jul 31, 20205.2.44No
EOL
5.1Jul 12, 2016-Apr 30, 20185.1.38No
EOL
5.0Jul 9, 2015-May 31, 20175.0.40No
EOL
4.3Oct 15, 2013-Dec 31, 20154.3.40No
EOL
4.2Sep 13, 2012-Dec 31, 20154.2.38No
EOL
4.1Jul 19, 2011-Dec 31, 20154.1.44No
EOL
4.0Dec 22, 2010-Dec 31, 20154.0.36No
EOL

Frequently Asked Questions

Which versions of VirtualBox have reached end of life?
The following VirtualBox versions have reached end of life and no longer receive security updates: 7.0, 6.1, 6.0, 5.2, 5.1, 5.0, 4.3, 4.2 (and 2 more). It is recommended to upgrade to a supported version.
Is it safe to continue using VirtualBox 7.0?
VirtualBox 7.0 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 VirtualBox?
The latest version of VirtualBox is 7.2.6, released in the 7.2 release cycle.
How many versions of VirtualBox are currently supported?
VirtualBox currently has 2 actively supported version(s): 7.2, 7.1.
When does VirtualBox 7.2 reach end of life?
VirtualBox 7.2 does not have a specific end-of-life date announced yet.
What should I do when VirtualBox reaches end of life?
When a VirtualBox 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.