php2shell patches (CVE-2026-109618 and CVE-2026-109619) for EOL PHP are out now. With sales replies slower than usual due to high demand, the fastest route to patched packages is to buy ELS for Runtimes online (opens in new tab). Read the patch FAQ

Endless Lifecycle Support

Endless Lifecycle Support for Language Ecosystems

Stop EOL Dependencies From
Becoming Your Biggest Security Gap

Patch out-of-support libraries for secure, audit-ready systems while
avoiding costly rewrites, rushed upgrades, and unnecessary risk.

Supported Ecosystems

  • JavaScript
  • Java
  • Python
  • PHP
  • Go
  • Rust
  • .Net
  • Perl
  • C++

If It’s Open Source and Not on Our List,

We’re Ready to Support It.
Just Ask.

What Does Endless Lifecycle Support Include?

With ELS, every release is secure, compatible, and built to industry standards you can trust.

Rapid CVE Response

Rapid SLA-backed security patches
for as long as you need

Complete Coverage

Security fixes for both direct and transitive EOL dependencies

Preserved Compatibility

Extensively tested updates that work flawlessly with your existing code

Seamless Integration

Plug-and-play integration with your workflows and CI/CD pipelines

Secure Distribution

Signed, tamper-proof updates from TuxCare-hosted repositories you can trust

Verifiable Provenance

Every release includes an SBOM, VEX, and SLSA Level 3 attestation**SLSA L3 attestation for ELS packages is coming soon

How Does It Work?

1

We onboard new projects and enable 24/7 automated CVE tracking – monitoring the NVD, vendor, and GitHub security advisories, and other sources.

2

Once CVEs are detected, we backport upstream fixes using algorithmic and AI-assisted automation, with expert validation to ensure accuracy.

3

Patches are compiled in a binary format, extensively tested (for integrity, functionality, and regression), signed, and deployed to ELS repositories.

4

Your package managers, build tools, or orchestrators check for updates, then automatically pull and install them.

Coverage That Reaches the Deepest Dependency

The EOL library you know about is rarely the whole problem. Its dependency set shifts with the functionality you use, and every vulnerable node means rebuilding everything above it.

ELS covers the whole ecosystem, the library you came for, every dependency it pulls in, and the EOL libraries you adopt next, patched and rebuilt automatically.

Where Unsupported Software Hurts
and What Changes With ELS

Development Teams

Reduce technical overhead by avoiding unstable upgrades, shifting dependency requirements, and code rewrites

IT Security Teams

Maintain application security and compliance by eliminating exposure to vulnerabilities in end-of-life open source components

Product Teams

Keep your roadmap on track and accelerate feature delivery by eliminating the drag of non-strategic upgrades

Before End of Life

There's SecureChain

Start protection while your packages are still maintained, and make end of life a non-event.

Powered by Fifteen Years of Proven
Excellence in Open Source Security

  • 0+ Vulnerabilities Fixed
  • 0+ Patches Delivered
  • 0+ Packages Curated

Trusted by Innovators Around the World

Related Resources

View all →

FedRAMP POA&M Entry and Closure When a Component Gets Patched

November 11, 2026

Key Takeaways Rev5 providers keep the legacy POA&M until they adopt FedRAMP’s 2026 vulnerability rules, which are required starting December 7, 2026. A scanner finding fixed before it’s past due needs no entry on the legacy POA&M, and a listed one closes once evidence of the fix is ready. Routine library patching skips agency approval […]

Learn more →

The CRA Expects Due Diligence on Open Source Code You Didn’t Write

November 10, 2026

Key Takeaways Article 13(5) of the Cyber Resilience Act (CRA) requires due diligence on third-party components, open source included. Breaching Article 13 risks fines up to EUR 15 million or 2.5% of global annual turnover, whichever is higher. Non-binding Recital 34 ties due diligence to component risk and names four possible actions, but the method […]

Learn more →

November 11 Node.js Security Updates for Supported and End of Life Versions

November 10, 2026

ELS Builds for the November Node.js Fixes Are Planned for Release Day Fixed builds for every affected Node.js line in the CloudLinux and TuxCare repositories, end-of-life versions included, are expected on November 11, shortly after the upstream release. ELS for Runtimes status: The team plans to ship all affected versions in a single run on […]

Learn more →

Talk to a TuxCare Expert

Tell us your challenges, and our experts will help you find the best approach to address them with the TuxCare product line.