Forkward

Security support for end-of-life PostgreSQL

PostgreSQL 14 reaches end of life on 12 November 2026, a year after PostgreSQL 13. After that date the PostgreSQL project publishes no more fixes for it. These are the versions still in use, with every vulnerability the US National Vulnerability Database lists for them.

Request a server assessment

PostgreSQL versions past end of life

PostgreSQLShips withEnd of lifeKnown CVEsCriticalExploitedForkward
9.2.24CentOS 7, RHEL 7, Oracle Linux 7 and Amazon Linux 29 November 20171820Patch on order, 48 h
9.6.24Last PostgreSQL 9.6 release11 November 20211000Patch on order, 48 h
10.23Last PostgreSQL 10 release10 November 20221000Patch on order, 48 h
11.22Last PostgreSQL 11 release9 November 2023800Patch on order, 48 h
12.22Last PostgreSQL 12 release21 November 2024800Patch on order, 48 h
13.23Last PostgreSQL 13 release13 November 2025800Patch on order, 48 h
14.24Last PostgreSQL 14 release12 November 2026000Patch on order, 48 h

Vulnerabilities from the US National Vulnerability Database, 28 October 2026, for the upstream version, counting only entries where PostgreSQL itself is the vulnerable product. Exploited: listed in the CISA catalogue of known exploited vulnerabilities. Package versions from each distribution's public repositories. Distribution builds include some vendor fixes; your assessment shows which risks are real.

Managed databases

On Amazon RDS or Azure, the provider controls the engine and charges for extended support. We patch the databases you run on your own servers and virtual machines. All databases

Patch on order, 48 h

We backport the fix to the version you run within 48 hours of your order, or within 24 hours with priority delivery. See the plans