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

TuxCare keeps you ahead of threats by proactively tracking and patching new CVEs impacting PostgreSQL. View all security fixes available to date here.

Keep Running.
Skip the Risks.

Upgrading end-of-life open-source runtimes, libraries, and
applications can be disruptive, resource-intensive, and costly.

TuxCare’s ELS keeps your legacy and EOL
components secure, compliant, and stable – without
the risks of costly upgrades.

What Does Endless Lifecycle Support Include?

Rapid CVE Response

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

Complete Coverage

Security fixes for both direct and transitive dependencies in PostgreSQL AT NO EXTRA COST

Preserved Compatibility

Extensively tested updates designed to work flawlessly with your existing code

Seamless Integration

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

Secure Distribution

Signed, tamper-proof PostgreSQL security updates delivered from trusted, TuxCare-hosted repositories

Trusted Support

24/7 expert assistance with PostgreSQL vulnerability triage, security patch requests, and troubleshooting

Secure Every Layer of Your OSS
Dependency Tree for the Long Run

End-of-life risk rarely lives in your top-level packages. It hides in the transitive
dependencies woven throughout your open-source stack.

When one of those libraries becomes vulnerable, every downstream component
must be rebuilt and validated.

TuxCare automates this entire process – tracking vulnerable EOL
libraries, applying security fixes, and rebuilding dependent components
– ensuring your full dependency chain stays secure and stable.

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.

Built for Your Stack

ELS for PostgreSQL is built to install easily and run with your existing workflows

TuxCare has successfully resolved

more than 14,000 CVEs

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

Check It Out

We’ve Been Powering Enterprise-Grade Patching At
Unprecedented Scale – and We're Just Getting Started

2,700+
Enterprise Clients

70,000+Packages Curated

420,000+
Patches Delivered

14,000+
Vulnerabilities Fixed

11,000+
Kernels Supported

70+
Linux Distro Versions Supported

Why TuxCare?

15 years of proven excellence in open-source patching have created highly
automated processes and systems, providing:

Extensive Coverage of Open-Source Technologies

We provide long-term security across your entire stack, supporting a wide and continually expanding set of open-source projects, libraries, and runtimes – all from a single, trusted partner.

Efficiencies in Build Chains and Testing

We utilize advanced automation across CVE discovery, backporting, building, and release workflows to accelerate delivery and ensure the highest possible quality of security patches.

Identification and Patching of Transitive Dependencies

We go beyond surface-level scanning to uncover and fix hidden vulnerabilities deep in your dependency trees, securing the entire software supply chain with precision and scale.

Fast and Consistent Delivery of Patches with Supporting SLAs

Automated pipelines and mature workflows ensure rapid, reliable patch delivery backed by SLAs – giving you confidence in your risk management and compliance posture.

Frequently Asked Questions

November 13, 2025. The PostgreSQL community supports each major version for five years, ships one final minor release, then retires the branch. Any CVE disclosed against 13 after that date goes permanently unpatched upstream. ELS for PostgreSQL delivers ongoing CVE fixes for PostgreSQL 13 past its EOL date.

Both, as separate products. ELS for PostgreSQL covers the PostgreSQL 13 database server, delivered through your package manager. TuxCare separately covers the PostgreSQL JDBC driver — versions 42.2.16 and 42.5.0, distributed as Maven and Gradle artifacts — for Java applications pinned to an older driver.

Yes, and this is where Postgres differs from most software. Major versions change the on-disk storage format, so moving forward means pg_upgrade or logical replication, real downtime, extension compatibility checks, and query-plan regression risk. TuxCare backports fixes into 13 instead.

That's the stated plan. PostgreSQL 14 reaches EOL in November 2026, and TuxCare has said it will extend the same coverage ahead of that date. Contact sales to confirm timing for your environment.

No. Updates arrive through your existing package manager as in-place minor updates within the same major version. Configuration, extensions, and replication topology are preserved, and no application changes are needed.

Managed-service extended support carries per-instance surcharges, varies by provider, and ends in a mandatory auto-upgrade on the provider's schedule. ELS covers self-managed and hybrid deployments, has no forced-migration date, and holds a fixed price for the contract term.

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.