Complete end-of-life dates, support windows, and security status for all Openssl versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.9.8 | 0.9.8zh | Jul 5, 2005 | Dec 31, 2015 | 3782 days past EOL | EOL |
| 1.0.0 | 1.0.0t | Mar 29, 2010 | Dec 31, 2015 | 3782 days past EOL | EOL |
| 1.0.1 | 1.0.1u | Mar 14, 2012 | Dec 31, 2016 | 3416 days past EOL | EOL |
| 1.0.2 LTS | 1.0.2u | Jan 22, 2015 | Dec 31, 2019 | 2321 days past EOL | EOL |
| 1.1.0 | 1.1.0l | Aug 25, 2016 | Sep 11, 2019 | 2432 days past EOL | EOL |
| 1.1.1 LTS | 1.1.1w | Sep 11, 2018 | Sep 11, 2023 | 971 days past EOL | EOL |
| 3.0 LTS | 3.0.20 | Sep 7, 2021 | Sep 7, 2026 | 121 days remaining | Warning |
| 3.1 | 3.1.8 | Mar 14, 2023 | Mar 14, 2025 | 421 days past EOL | EOL |
| 3.2 | 3.2.6 | Nov 23, 2023 | Nov 23, 2025 | 167 days past EOL | EOL |
| 3.3 | 3.3.7 | Apr 9, 2024 | Apr 9, 2026 | 30 days past EOL | EOL |
| 3.4 | 3.4.5 | Oct 22, 2024 | Oct 22, 2026 | 166 days remaining | Warning |
| 3.5 LTS | 3.5.6 | Apr 8, 2025 | Apr 8, 2030 | 1430 days remaining | Active |
| 3.6 | 3.6.2 | Oct 1, 2025 | Nov 1, 2026 | 176 days remaining | Warning |
| 4.0 | 4.0.0 | Apr 14, 2026 | May 14, 2027 | 370 days remaining | Active |
When a Openssl version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Openssl should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →