OPENSSL COVERAGE

OpenSSL 3.0 LTS is end of life. Your patching does not have to be.

OpenSSL extended support from OSSeva covers OpenSSL 3.0, the LTS line that reached end of life on 7 September 2026. The OpenSSL project now releases 3.0 fixes only to premium support customers, so every public 3.0 build sits inside the affected range of later CVEs. Send your work email and an engineer replies within 1 business day with coverage for your OpenSSL version.

Who it is forTeams whose scanner or auditor flags OpenSSL 3.0.x, running it in an appliance, container image, language runtime or vendor product they cannot rebuild on OpenSSL 3.5 yet
What you getSigned patched OpenSSL 3.0 builds, with the same MAJOR version and ABI so applications are not recompiled. Assure adds an exposure audit, SBOM and audit evidence, and an upgrade path assessment.
How it is pricedPer application runtime. Ask for a quote.
What happens nextYou send your work email, we confirm where OpenSSL 3.0 sits in your stack, and you get a coverage plan.

Reply within 1 business day · No commitment · or book a 15-minute call

Last reviewed

Only your email is required · An engineer replies within 1 business day · No commitment

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

OpenSSL support dates, read on 19 November 2026

The OpenSSL release strategy page gives end dates for the supported lines and says 3.0, 1.1.1 and 1.0.2 are no longer supported. Dates for lines that already ended, and the 3.0 end date, are from endoflife.date.

LineTypeEnd of supportSource
3.0LTS7 Sep 2026 (last public release 3.0.22, 25 Aug 2026)endoflife.date; openssl-library.org lists it as no longer supported
3.5LTS8 Apr 2030openssl-library.org
4.0Non-LTS14 May 2027openssl-library.org
4.1Non-LTS23 Nov 2027openssl-library.org

OpenSSL end-of-life dates for every line →openssl-library.org: release strategy →

OpenSSL CVEs since 3.0 ended, with no public 3.0 fix

Each CVE record and the matching OpenSSL advisory list OpenSSL 3.0 as affected and give the fixed 3.0 release as 3.0.23 or 3.0.24, which the advisory restricts to premium support customers. The newest public 3.0 release is 3.0.22, so a public 3.0 build is inside every range below.

CVEIssueSeverityFix for 3.0
CVE-2026-84782DTLS retransmits handshake messages from a stale buffer offsetHigh3.0.23, premium support customers only (advisory of 29 Sep 2026)
CVE-2026-107496Infinite loop in CMS_encrypt() with an EC group order of 1Low3.0.24, premium support customers only (advisory of 10 Nov 2026)
CVE-2026-107493Use-after-free in PEM_X509_INFO_read_bio_ex() when appending to a caller-supplied stack failsLow3.0.24, premium support customers only (advisory of 17 Nov 2026)

Sources: cveawg.mitre.org records for each CVE, and openssl-library.org/news/secadv/ advisories 20260929, 20261110 and 20261117; severity is OpenSSL's rating. Whether an application is exposed depends on which functions it calls. If you run OpenSSL from a Linux distribution package, check the distributor's own security tracker, because a distributor can fix issues under its own package version.

openssl-library.org: vulnerabilities →

Which runtimes carry OpenSSL

A scanner reports OpenSSL separately from the language that bundles or links it. Each statement below is from the project's own page, read on 19 November 2026.

RuntimeWhat the project saysSource
Node.jsBundles its own OpenSSL. The latest 22, 24 and 26 releases (22.23.5, 24.22.3 and 26.13.1, 10 to 11 Nov 2026) bundle OpenSSL 3.5.9. The last Node.js 20 release, 20.20.2 of 24 Mar 2026, bundles 3.0.19.nodejs.org/dist/index.json
PythonThe hashlib, hmac and ssl modules use OpenSSL. Python 3.10 and later support only OpenSSL 1.1.1 LTS or newer.PEP 644
RubyThe openssl library is a wrapper around OpenSSL. Its current 4.0.x gem line supports OpenSSL 1.1.1 to 4.x.github.com/ruby/openssl
PHPPHP 8.1 and later require OpenSSL below 4.0, and PHP 8.4 requires 1.1.1 or newer.php.net manual, OpenSSL requirements

Node.js extended support →Python extended support →PHP extended support →Ruby extended support →

Why now

OpenSSL 3.0 LTS reached end of life on 7 September 2026

OpenSSL 3.0.0 was released on 7 September 2021, and endoflife.date lists 7 September 2026 as the end of the line. The OpenSSL release strategy page lists 3.0 among the versions that are no longer supported. The last public release is 3.0.22 of 25 August 2026.

Fixes for 3.0 now go to premium support customers only

The OpenSSL advisories of 29 September, 10 November and 17 November 2026 list OpenSSL 3.0.23 and 3.0.24 under "Premium support customers only". The public upgrade targets are 3.5, 4.0 and 4.1. The OpenSSL release strategy page says extended support for 3.0, 1.1.1 and 1.0.2 is available.

Python, Node.js, Ruby and PHP all depend on it

A runtime that bundles or links OpenSSL carries the version in its own build. Node.js 20, which ended on 30 April 2026, last shipped with OpenSSL 3.0.19. Moving the runtime does not always move OpenSSL with it, and a scanner reports the library separately from the language.

Versions covered

All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.

VersionStatusActive CVEs
3.0(Community EOL 7 Sep 2026 (last public release 3.0.22))EOLClean
3.5(LTS, supported until 8 Apr 2030. Assessed case by case.)CurrentClean
OpenSSL end of life dates for every version →

Running a OpenSSL version or build not listed here?

What you get

Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.

OSSeva Patch

Security patches for OpenSSL 3.0 after end of life.

  • Backported security fixes for OpenSSL 3.0
  • Critical CVEs fixed within 48 hours, High within 7 days
  • Signed artifacts (GPG + Sigstore)
  • CVE disclosure notifications
  • Architecture review
  • 24/7 managed operations
Most popular

OSSeva Assure

Patch plus compliance documentation and upgrade planning.

  • Everything in Patch
  • SOC 2 / HIPAA attestation package
  • OpenSSL upgrade path assessment
  • 24/7 reactive support

OSSeva Operate

Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.

  • Everything in Assure
  • 24/7 application and runtime monitoring
  • 15-minute P1 incident response SLA
  • Named senior engineer on your account

All tiers priced per cluster/application — not per core.

Compliance library

📄SOC 2 compliance evidence package
Request →
📄Sample Audit Narrative
Request →
📄Pen-Test Report Summary
Request →
📄HIPAA Technical Safeguard Matrix
Request →

Questions

Frequently asked questions

Book a 15-minute call

Which OpenSSL versions does OSSeva patch?

OpenSSL 3.0 after end of life. Other versions are assessed case by case through a version coverage check.

How fast are OpenSSL vulnerabilities patched?

Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.

Does OpenSSL provide its own extended support for 3.0?

Yes. The OpenSSL release strategy page says extended support for 3.0, 1.1.1 and 1.0.2 is available, and its security advisories mark the fixed 3.0 releases as for premium support customers only (both read on 19 November 2026). OSSeva is an alternative if you want patching delivered with the rest of your runtime estate.

Does patching OpenSSL also patch Node.js, Python, Ruby or PHP?

Only where the runtime uses the shared library. Node.js bundles its own OpenSSL, so it needs a runtime release or a patched runtime. See the Node.js, Python and PHP pages for the runtimes themselves.

How is OSSeva OpenSSL support priced?

It is priced per application runtime. Request a quote and a senior engineer replies within 1 business day.

Get a quote

Ready to get OpenSSL patched and supported?

Tell us your OpenSSL versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call