← ← Back to all products
OpenVPN
Active
Server Software Latest Version: 2.7.0 Latest Release: Feb 11, 2026
OpenVPN is an open-source VPN solution for creating secure point-to-point or site-to-site connections.
Versions
7
Latest Version
2.7.0
Active Support
2
EOL
5
Lifecycle Timeline
Today ↓
2.7
2.7
2.6
2.6
2.5
2.5
2.4
2.4
2.3
2.3
2.2
2.2
2.1
2.1
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2.7 | Feb 11, 2026 | Yes | No | 2.7.0 | No | Active |
| 2.6 | Jan 25, 2023 | Aug 31, 2026 | Aug 31, 2028 | 2.6.19 | No | Active |
| 2.5 | Oct 27, 2020 | Jul 18, 2024 | Jul 31, 2025 | 2.5.11 | No | EOL |
| 2.4 | Dec 16, 2016 | Mar 17, 2022 | Mar 31, 2023 | 2.4.12 | No | EOL |
| 2.3 | Jan 2, 2013 | Sep 25, 2017 | Jun 30, 2021 | 2.3.18 | No | EOL |
| 2.2 | Apr 21, 2011 | Nov 30, 2014 | Nov 30, 2015 | 2.2.3 | No | EOL |
| 2.1 | Dec 11, 2009 | Nov 6, 2010 | Nov 30, 2011 | 2.1.4 | No | EOL |
Frequently Asked Questions
Which versions of OpenVPN have reached end of life?
The following OpenVPN versions have reached end of life and no longer receive security updates: 2.5, 2.4, 2.3, 2.2, 2.1. It is recommended to upgrade to a supported version.
Is it safe to continue using OpenVPN 2.5?
OpenVPN 2.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 OpenVPN?
The latest version of OpenVPN is 2.7.0, released in the 2.7 release cycle.
How many versions of OpenVPN are currently supported?
OpenVPN currently has 2 actively supported version(s): 2.7, 2.6.
When does OpenVPN 2.7 reach end of life?
OpenVPN 2.7 does not have a specific end-of-life date announced yet.
What should I do when OpenVPN reaches end of life?
When a OpenVPN 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.