PostgreSQL end-of-life dates, and what to do when yours expires

PostgreSQL EOL has passed for 14 and every older version: 14 reached end of life on 12 November 2026 with 14.25, its final release, and 15 to 18 are supported to November 2027, 2028, 2029 and 2030. The four 2026 minor-release sets fixed 96 CVEs, and 13, 12 and 11 received none of them. Dates checked against endoflife.date and postgresql.org on 14 November 2026.

The PostgreSQL Global Development Group supports each major version for five years after its first release, then ships a final minor release and declares it end of life. Minor releases with bug and security fixes come out at least once every three months, and a new major version arrives about once a year.

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

Latest release
18.7
Supported lines
4
End-of-life lines
28
Next end of life
15 · 11 Nov 2027

PostgreSQL 14 ended on 12 November 2026

Running PostgreSQL 14? Start here.

The four 2026 minor-release sets fixed 96 CVEs, 66 of them rated 7.0 or higher, and PostgreSQL 13, 12 and 11 received none of those fixes. 14 received the last of them in 14.25, its final release on 12 November, and gets no more. The 14 page has the exact dates, the Amazon RDS and Azure cut-offs and the upgrade options.

Who patches PostgreSQL after end of life

OSSeva provides PostgreSQL extended support: patched, signed builds for PostgreSQL 14, 13, 12 and 11 after upstream support ends, plus 24/7 operations on the Operate tier.

PostgreSQL release timeline

Support StatusTodayChart shows the 14 newest lines; the table lists all.

All PostgreSQL versions, release dates and end-of-life dates

VersionReleasedSupport StatusLatestOSSeva
181 year and 2 months ago(25 Sept 2025)Ends in 4 years(14 Nov 2030)18.7–
17PostgreSQL 17 end of life2 years and 2 months ago(26 Sept 2024)Ends in 3 years(8 Nov 2029)17.12–
16PostgreSQL 16 end of life3 years and 2 months ago(14 Sept 2023)Ends in 2 years(9 Nov 2028)16.16–
15PostgreSQL 15 end of life4 years and 1 month ago(13 Oct 2022)Ends in 1 year(11 Nov 2027)15.20–
14PostgreSQL 14 end of life5 years and 2 months ago(30 Sept 2021)Ended 4 days ago(12 Nov 2026)14.25 Patched
13PostgreSQL 13 end of life6 years and 2 months ago(24 Sept 2020)Ended 1 year ago(13 Nov 2025)13.23 Patched
12PostgreSQL 12 end of life7 years and 1 month ago(3 Oct 2019)Ended 2 years ago(21 Nov 2024)12.22 Patched
11PostgreSQL 11 end of life8 years and 1 month ago(18 Oct 2018)Ended 3 years ago(9 Nov 2023)11.22 Patched
109 years and 1 month ago(5 Oct 2017)Ended 4 years ago(10 Nov 2022)10.23–
9.610 years and 2 months ago(29 Sept 2016)Ended 5 years ago(11 Nov 2021)9.6.24–
9.510 years and 10 months ago(7 Jan 2016)Ended 5 years and 9 months ago(11 Feb 2021)9.5.25–
9.411 years and 11 months ago(18 Dec 2014)Ended 6 years and 9 months ago(13 Feb 2020)9.4.26–
9.313 years and 2 months ago(9 Sept 2013)Ended 8 years ago(8 Nov 2018)9.3.25–
9.214 years and 2 months ago(10 Sept 2012)Ended 9 years ago(9 Nov 2017)9.2.24–
9.115 years and 2 months ago(12 Sept 2011)Ended 10 years and 1 month ago(27 Oct 2016)9.1.24–
9.016 years and 2 months ago(20 Sept 2010)Ended 11 years and 1 month ago(8 Oct 2015)9.0.23–
8.417 years and 5 months ago(1 Jul 2009)Ended 12 years and 4 months ago(24 Jul 2014)8.4.22–
8.318 years and 9 months ago(4 Feb 2008)Ended 13 years and 9 months ago(7 Feb 2013)8.3.23–
8.219 years and 11 months ago(5 Dec 2006)Ended 14 years and 11 months ago(5 Dec 2011)8.2.23–
8.121 years ago(8 Nov 2005)Ended 16 years ago(8 Nov 2010)8.1.23–
8.021 years and 10 months ago(19 Jan 2005)Ended 16 years and 1 month ago(1 Oct 2010)8.0.26–
7.423 years ago(17 Nov 2003)Ended 16 years and 1 month ago(1 Oct 2010)7.4.30–
7.324 years ago(27 Nov 2002)Ended 19 years ago(27 Nov 2007)7.3.21–
7.224 years and 9 months ago(4 Feb 2002)Ended 19 years and 9 months ago(4 Feb 2007)7.2.8–
7.125 years and 7 months ago(13 Apr 2001)Ended 20 years and 7 months ago(13 Apr 2006)7.1.3–
7.026 years and 6 months ago(8 May 2000)Ended 21 years and 6 months ago(8 May 2005)7.0.3–
6.527 years and 5 months ago(9 Jun 1999)Ended 22 years and 5 months ago(9 Jun 2004)6.5.3–
6.428 years and 1 month ago(30 Oct 1998)Ended 23 years and 1 month ago(30 Oct 2003)6.4.2–
6.328 years and 9 months ago(1 Mar 1998)Ended 23 years and 9 months ago(1 Mar 2003)6.3.2–
6.229 years and 1 month ago(2 Oct 1997)Ended6.2.1–
6.129 years and 5 months ago(8 Jun 1997)Ended6.1.1–
6.029 years and 10 months ago(29 Jan 1997)Ended6.0–

Lifecycle data from endoflife.date (MIT licence), refreshed 15 Nov 2026. Upstream policy: www.postgresql.org. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.

What end of life means for PostgreSQL

The PostgreSQL Global Development Group supports each major version for five years after its first release. It then ships one final minor release and stops: no more security fixes, no more fixes for data-corruption bugs, and no more minor releases at all. The project considers running an old minor release riskier than upgrading it.

Managed services add their own dates on top of the community date. Amazon RDS and Aurora keep patching an ended version for a fee, and Azure does the same, so a database can be past community end of life and still receive fixes, for as long as you keep paying for them.

CVEs fixed after each version ended

The four 2026 minor-release sets (12 February, 14 May, 13 August and 12 November) fixed 96 CVEs, and PostgreSQL scored 66 of them 7.0 or higher. All four sets came after 11, 12 and 13 ended, and none of the fixes has a release for those versions. The project's advisories list versions 14 to 18 as affected, so 11 to 13 are not assessed. That is not a finding that they are safe.

2026 PostgreSQL security fixes and the versions that missed them

VersionEndedFinal minor2026 CVEs fixed after it endedScored 7.0 or higherFix for this version
1313 Nov 202513.239666No release
1221 Nov 202412.229666No release
119 Nov 202311.229666No release

Source: the CVE table on postgresql.org/support/security, counted on 14 November 2026. Scores are PostgreSQL's own as the CNA. Counts cover 2026 only.

Upgrade, cloud extended support or patched builds

A PostgreSQL version that has ended can be upgraded, kept on a cloud provider's paid extended support, or kept patched on your own servers. Most estates end up using more than one, server by server.

OptionWhat it isIt fits whenThe catch
Upgrade to 17 or 18pg_upgrade or logical replication to a supported major, after an extension audit and a rehearsal.You can move the server before its date.Scope depends on schema size, extension use, code volume and the downtime window you can get.
Cloud extended supportAmazon RDS, Aurora and Azure keep patching an ended version and bill for it per vCPU-hour.The database already runs in that managed service and will stay there.Only inside that service, and the charge follows vCPU count and steps up in later years.
Patched builds from OSSevaSigned builds with backported security and data-corruption fixes for PostgreSQL 11, 12, 13 and, from 12 November 2026, 14.Self-managed PostgreSQL on VMs, bare metal, Kubernetes or EC2 that cannot all move in time.A subscription per cluster for as long as you stay on the version. It buys time and does not replace the upgrade.

Running an end-of-life PostgreSQL version?

OSSeva keeps end-of-life PostgreSQL patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.

PostgreSQL extended support

Questions

PostgreSQL end of life: common questions

Book a 15-minute call

Is PostgreSQL 13 still supported?

Not by the community. PostgreSQL 13 reached end of life on 13 November 2025 with 13.23, and the project ships no further security or bug fixes for it. Amazon RDS and Aurora sell paid Extended Support for 13, and for self-managed servers third-party providers backport fixes, including OSSeva.

Is PostgreSQL 18 released?

Yes. PostgreSQL 18 was released on 25 September 2025, and the current minor release is 18.7, from 12 November 2026. It is supported until 14 November 2030. PostgreSQL 19 is at release candidate 2 and had not reached general availability when checked on 12 November 2026; general availability is planned for 19 November 2026.

Which vendors offer extended security support for PostgreSQL 13 after it reached end of life?

For managed databases, Amazon RDS and Aurora enrol PostgreSQL 13 in paid Extended Support. For self-managed servers, third-party providers backport fixes to the 13 line, and OSSeva ships signed, patched builds for 11, 12 and 13, and for 14 after 12 November 2026.

How long is a PostgreSQL version supported?

Five years from its initial release. The PostgreSQL Global Development Group then publishes one final minor release for that major version, after which it is unsupported and gets no bug or security fixes. The versioning policy page lists the final release date for every major, and the table above follows it.

Is PostgreSQL 13 end of life?

Yes. PostgreSQL 13 reached end of life on 13 November 2025, five years after its September 2020 release, and 13.23 was its final minor release. The community no longer fixes bugs or security issues in 13, so the upstream path is a major upgrade with pg_upgrade or a dump and reload.

When is PostgreSQL 14 end of life?

postgresql.org lists 12 November 2026 as the final release date for PostgreSQL 14, five years after it shipped in September 2021. That final minor release ends community bug and security fixes for 14. Moving to a newer major version needs pg_upgrade or a dump and reload, as the versioning policy explains.

Do PostgreSQL minor upgrades need a dump and restore?

No. A minor upgrade, such as 16.14 to 16.15, means stopping the server, installing the new binaries and restarting, though the release notes may list extra steps. The PostgreSQL community considers running an old minor release riskier than upgrading. Major upgrades are different and need pg_upgrade or a dump and reload.

What is the latest PostgreSQL version?

18.7, released 9 Nov 2026, on the 18 line. Other supported lines: 17, 16 and 15.

When is the next PostgreSQL end of life?

PostgreSQL 15 reaches the end of support status on 11 Nov 2027. After that date the project stops shipping security fixes for 15, and CVEs disclosed later stay unpatched upstream.

Which PostgreSQL versions are still supported?

18 (until 14 Nov 2030), 17 (until 8 Nov 2029), 16 (until 9 Nov 2028) and 15 (until 11 Nov 2027). Every other line has reached end of life, per the dates in the table above.

Can I get security patches for an end-of-life PostgreSQL version?

Yes. OSSeva ships signed builds with backported CVE fixes for PostgreSQL 14, 13, 12 and 11 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.

Who provides PostgreSQL support after end of life?

OSSeva provides PostgreSQL extended support: patched, signed builds for PostgreSQL 14, 13, 12 and 11 after upstream support ends, plus 24/7 operations on the Operate tier.

Get a quote

Still running an end-of-life PostgreSQL?

Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.

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

Prefer to talk or read more first?

Book a call