Openssl 3.1 · Version Status
Openssl 3.1 End of Life Date
Openssl 3.1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Openssl 3.1 is past end of life. This version no longer receives security patches. 421 days past EOL — migrate to a supported version immediately.
EOL Date
Mar 14, 2025
421 days past EOL
Latest Release
3.1.8
Standard release
Release Date
Mar 14, 2023
Openssl 3.1 series
| Version | Latest | EOL Date | Status |
|---|
| 0.9.8 |
0.9.8zh |
Dec 31, 2015 |
EOL |
| 1.0.0 |
1.0.0t |
Dec 31, 2015 |
EOL |
| 1.0.1 |
1.0.1u |
Dec 31, 2016 |
EOL |
| 1.0.2 LTS |
1.0.2u |
Dec 31, 2019 |
EOL |
| 1.1.0 |
1.1.0l |
Sep 11, 2019 |
EOL |
| 1.1.1 LTS |
1.1.1w |
Sep 11, 2023 |
EOL |
| 3.0 LTS |
3.0.20 |
Sep 7, 2026 |
Warning |
| → 3.1 |
3.1.8 |
Mar 14, 2025 |
EOL |
What does Openssl 3.1 end of life mean?
When Openssl 3.1 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Openssl 3.1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Openssl 4.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Openssl 3.1 reach end of life?
Openssl 3.1 reached end of life on March 14, 2025. This version is no longer receiving security patches.
Is Openssl 3.1 still supported?
No. Openssl 3.1 reached end of life on March 14, 2025 and is no longer receiving security patches.
What should I upgrade to from Openssl 3.1?
The recommended upgrade from Openssl 3.1 is
Openssl 4.0 — the latest actively supported version. Check the
Openssl full timeline for all supported versions.
What are the security risks of running Openssl 3.1 past EOL?
When Openssl 3.1 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Openssl should migrate immediately or implement compensating controls.