Check the status of CVEs. Learn More.

 CVE Status (opens in new tab)

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

How We Keep You Secure

1. Detection

Continuous CVE monitoring

We onboard each supported runtime and enable 24/7 CVE tracking across multiple sources – including NVD, vendor advisories, GitHub security advisories, and more.
New vulnerabilities are identified as soon as they’re disclosed – not weeks later during a scan.
2. BACKPORTING

Expert-validated patch backporting

When a CVE is detected, we backport the upstream fix to your existing runtime version using algorithmic and AI-assisted automation, with expert validation to ensure accuracy.
You get the fix – without changing versions, breaking compatibility, or triggering a migration.
3. BUILD & TEST

Compiled, tested, signed & published

Each patch is compiled into a binary, then rigorously tested for integrity, functionality, and regression. Once validated, it’s signed and published to ELS repositories.
Patches are production-ready – stable, verified, and safe to deploy.
4. DELIVERY

Automatic delivery via your existing tooling

Your package managers, automatically check for updates and install patches as part of your normal processes.
No new tooling. No manual patching. No disruption to your pipeline.

Buy and ActivateELS for Runtimes Today

Buy online and activate on your own.No sales call, no waiting.

Purchase ELS Licenses

Supported Runtimes

Node.js
12 | 14 | 16 | 18 | 20
Python
2.7 | 3.3 | 3.4 | 3.5 | 3.6 | 3.7 | 3.8 | 3.9 | 3.10 | 3.11 | 3.12 | 3.13
PHP
5.2 - 8.4
.NET
6 | 8 | 10
OpenJDK
7 | 8 | 11 | 17
Ruby
2.6 | 2.7 | 3.0 | 3.1

TuxCare has successfully resolved

more than 14,000 CVEs

in open-source software – keeping enterprise systems secure and compliant

Stay secure (without rushing an upgrade)

Get a clear view of how ELS for Runtimes fits your environment and what coverage looks like for your stack.
Ask us a question

Common Questions

No. ELS patches are delivered through standard package repositories. Your existing package managers (apt, yum, pip, npm, etc.) pull updates automatically – no pipeline changes required.

Upgrades require code changes, testing, and migration effort across your entire stack. ELS provides security patches for the version you’re already running – no breaking changes, no migration cost, and no disruption.

No. ELS provides actual remediation – not just detection. We identify vulnerabilities, backport fixes, validate them, and deliver production-ready patches.

Each patch is tested for integrity, functionality, and regression before being signed and published to ELS repositories.

While patches are extensively tested before release, if an issue arises in your specific environment, our support team works directly with you to resolve it.

ELS extends security coverage after vendor support ends. It focuses specifically on vulnerability remediation, not full vendor support.

We continue tracking newly disclosed CVEs, backporting fixes, and delivering patches – so your runtime remains secure even after upstream support ends.