OpenSSL EOL: support dates for every OpenSSL version
OpenSSL 3.0 LTS reached end of life on 7 September 2026, and its last public release is 3.0.22 of 25 August 2026. The current LTS, OpenSSL 3.5, is supported until 8 April 2030. The OpenSSL project sells extended support for 3.0; OSSeva also patches it after end of life, and assesses other versions case by case. Dates checked on 19 November 2026.
- Latest release
- 4.1.0
- Supported lines
- 3
- End-of-life lines
- 12
- Next end of life
- 4.0 · 14 May 2027
OpenSSL 3.0 has ended; fixes now go to premium customers
Upgrade to 3.5, or keep OpenSSL 3.0 patched
Within the 3.x series OpenSSL keeps API and ABI compatibility, so many applications can move to 3.5 LTS. When a vendor product, appliance or runtime build pins 3.0, OSSeva patches it. Other OpenSSL versions are assessed case by case. Critical fixes ship within 48 hours and High within 7 days.
Who patches OpenSSL after end of life
OSSeva provides OpenSSL extended support: patched, signed builds for OpenSSL 3.0 after upstream support ends, plus 24/7 operations on the Operate tier.
OpenSSL release timeline
All OpenSSL versions, release dates and end-of-life dates
| Version | Released | Supported | Latest | OSSeva |
|---|---|---|---|---|
| 4.1 | 29 days ago(23 Oct 2026) | Ends in 1 year(23 Nov 2027) | 4.1.0 | – |
| 4.0 | 7 months ago(14 Apr 2026) | Ends in 6 months(14 May 2027) | 4.0.3 | – |
| 3.6 | 1 year and 2 months ago(1 Oct 2025) | Ended 20 days ago(1 Nov 2026) | 3.6.5 | – |
| 3.5 (LTS) | 1 year and 7 months ago(8 Apr 2025) | Ends in 3 years and 5 months(8 Apr 2030) | 3.5.9 | – |
| 3.4 | 2 years and 1 month ago(22 Oct 2024) | Ended 30 days ago(22 Oct 2026) | 3.4.8 | – |
| 3.3 | 2 years and 7 months ago(9 Apr 2024) | Ended 7 months ago(9 Apr 2026) | 3.3.7 | – |
| 3.2 | 3 years ago(23 Nov 2023) | Ended 1 year ago(23 Nov 2025) | 3.2.6 | – |
| 3.1 | 3 years and 8 months ago(14 Mar 2023) | Ended 1 year and 8 months ago(14 Mar 2025) | 3.1.8 | – |
| 3.0 (LTS) | 5 years and 2 months ago(7 Sept 2021) | Ended 2 months ago(7 Sept 2026) | 3.0.22 | Patched |
| 1.1.1 (LTS) | 8 years and 2 months ago(11 Sept 2018) | Ended 3 years and 2 months ago(11 Sept 2023) | 1.1.1w | – |
| 1.1.0 | 10 years and 3 months ago(25 Aug 2016) | Ended 7 years and 2 months ago(11 Sept 2019) | 1.1.0l | – |
| 1.0.2 (LTS) | 11 years and 10 months ago(22 Jan 2015) | Ended 6 years and 11 months ago(31 Dec 2019) | 1.0.2u | – |
| 1.0.1 | 14 years and 8 months ago(14 Mar 2012) | Ended 9 years and 11 months ago(31 Dec 2016) | 1.0.1u | – |
| 1.0.0 | 16 years and 8 months ago(29 Mar 2010) | Ended 10 years and 11 months ago(31 Dec 2015) | 1.0.0t | – |
| 0.9.8 | 21 years and 5 months ago(5 Jul 2005) | Ended 10 years and 11 months ago(31 Dec 2015) | 0.9.8zh | – |
Lifecycle data from endoflife.date (MIT licence), refreshed 21 Nov 2026. Upstream policy: openssl-library.org. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.
OpenSSL 3.0, 3.5 and 4.x support dates
OpenSSL designates a long-term support release every two years and supports it for at least five years, with only security fixes in the final year (openssl-library.org/policies/releasestrat). Non-LTS releases after 3.5 are fully supported for 13 months. OpenSSL 3.0 is the earlier LTS and 3.5 the current one; 3.0 is no longer supported, and the release strategy page says extended support for 3.0, 1.1.1 and 1.0.2 is available.
OpenSSL support dates. Source: openssl-library.org/policies/releasestrat, read on 19 November 2026, and endoflife.date for lines that already ended and for the LTS flags.
| Version | Type | Released | End of support |
|---|---|---|---|
| OpenSSL 1.1.1 | LTS | 11 Sep 2018 | 11 Sep 2023 (last release 1.1.1w) |
| OpenSSL 3.0 | LTS | 7 Sep 2021 | 7 Sep 2026 (last public release 3.0.22) |
| OpenSSL 3.5 | LTS | 8 Apr 2025 | 8 Apr 2030 |
| OpenSSL 4.0 | Non-LTS | 14 Apr 2026 | 14 May 2027 |
| OpenSSL 4.1 | Non-LTS | 23 Oct 2026 | 23 Nov 2027 |
The OpenSSL release strategy page gives no end date for 3.0; its date here is from endoflife.date, and equals five years from the 3.0.0 release. The lines between, 3.1 to 3.4 and 3.6, have also ended per endoflife.date.
What changed when OpenSSL 3.0 ended
OpenSSL does not stop issuing 3.0 fixes; it stops issuing them publicly. The advisory of 25 August 2026 gave 3.0.22 as the upgrade for 3.0 users. The advisories of 29 September, 10 November and 17 November 2026 list 3.0.23 and 3.0.24 under premium support customers only, next to 1.1.1 and 1.0.2 builds. The public targets are the supported lines: 3.5, 4.0 and 4.1. So every public 3.0 build, 3.0.22 and earlier, is inside the affected range of CVE-2026-84782, a High-severity DTLS flaw, and of two Low-severity CVEs published in November.
That matters for scanners more than for most attackers. A scanner reads the version string, finds 3.0.22 in a range that lists 3.0 as fixed only at 3.0.23 or 3.0.24, and raises a finding that has no public remedy. Whether the flaw is reachable depends on what the application calls: the DTLS issue needs DTLS, and the PEM issue needs an application that passes an existing stack to PEM_X509_INFO_read_bio_ex(). The finding remains until the version moves or a patched build is installed. If OpenSSL comes from a Linux distribution package, check that distributor's own security tracker first, because the version string may not tell the whole story there.
Moving to 3.5 LTS is the lower-effort upgrade. OpenSSL guarantees API and ABI compatibility within the same MAJOR version and allows no breaking change in a minor or patch release, so 3.0 to 3.5 is a minor-version move. OpenSSL 4.0 is a new major version with incompatible changes allowed. The PHP manual states that PHP 8.1 and later require OpenSSL below 4.0, so a PHP estate that wants off 3.0 should target 3.5, not 4.x.
Runtimes complicate the picture. Node.js bundles its own OpenSSL: the latest 22, 24 and 26 releases carry 3.5.9, while the last Node.js 20 release, 20.20.2 of 24 March 2026, carries 3.0.19, three patch releases behind the 3.0.22 that OpenSSL had shipped by August. Upgrading the base image does not change the OpenSSL inside a Node.js binary.
Who patches OpenSSL 3.0 after end of life?
The OpenSSL project does, for customers of its premium support: its release strategy page says extended support for 3.0, 1.1.1 and 1.0.2 is available, and its support plans page lists extended LTS release coverage in its top two plans (both read on 19 November 2026). OSSeva also patches OpenSSL 3.0 after end of life and assesses other versions case by case through a version coverage check. OSSeva delivers it alongside the runtimes that embed OpenSSL, priced per application runtime. Critical fixes ship within 48 hours and High within 7 days.
Running an end-of-life OpenSSL version?
OSSeva keeps end-of-life OpenSSL patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.
OpenSSL extended supportIs OpenSSL 3.0 end of life?
Yes. OpenSSL 3.0 LTS reached end of life on 7 September 2026 per endoflife.date, and the OpenSSL release strategy page lists it as no longer supported. Its last public release is 3.0.22, from 25 August 2026.
When does OpenSSL 3.5 reach end of life?
8 April 2030. OpenSSL 3.5 is the current LTS release, and the OpenSSL policy covers an LTS release for at least five years, with only security fixes in the last year.
Which OpenSSL versions are LTS?
OpenSSL 3.0 and 3.5 are LTS among current lines, and 1.1.1 and 1.0.2 were LTS lines that ended earlier. OpenSSL designates an LTS release every two years and supports it for at least five years.
Is OpenSSL 1.1.1 end of life?
Yes. OpenSSL 1.1.1 reached end of life on 11 September 2023 and its last release was 1.1.1w. The OpenSSL project says extended support for it is available to premium support customers.
Which OpenSSL version does Node.js use?
Node.js bundles its own copy. The latest Node.js 22, 24 and 26 releases bundle OpenSSL 3.5.9, and the last Node.js 20 release, 20.20.2, bundles 3.0.19, per the nodejs.org release index read on 19 November 2026. See Node.js end-of-life dates.
Who provides OpenSSL 3.0 support after end of life?
The OpenSSL project provides extended support to premium support customers. OSSeva also patches OpenSSL 3.0 after end of life and assesses other versions case by case through a version coverage check.
What is the latest OpenSSL version?
4.1.0, released 23 Oct 2026, on the 4.1 line. Other supported lines: 4.0 and 3.5.
When is the next OpenSSL end of life?
OpenSSL 4.0 reaches the end of supported on 14 May 2027. After that date the project stops shipping security fixes for 4.0, and CVEs disclosed later stay unpatched upstream.
Which OpenSSL versions are still supported?
4.1 (until 23 Nov 2027), 4.0 (until 14 May 2027) and 3.5 (until 8 Apr 2030). Every other line has reached end of life, per the dates in the table above.
Can I get security patches for an end-of-life OpenSSL version?
Yes. OSSeva ships signed builds with backported CVE fixes for OpenSSL 3.0 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.
Who provides OpenSSL support after end of life?
OSSeva provides OpenSSL extended support: patched, signed builds for OpenSSL 3.0 after upstream support ends, plus 24/7 operations on the Operate tier.
Get a quote
Still running an end-of-life OpenSSL?
Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.
Prefer to talk or read more first?