PostgreSQL 14 end of life
PostgreSQL 14 reaches end of life on 12 November 2026. The community ships its final 14.x minor release that week, then no more security, bug or data-corruption fixes. On Amazon RDS and Aurora, standard support for 14 runs to 28 February 2027 and paid Extended Support starts on 1 March 2027. Dates checked 20 October 2026. PostgreSQL 19 is at release candidate 1, with general availability planned for 19 November 2026.
What now
Which vendors provide PostgreSQL 14 security patches after 12 November 2026?
PostgreSQL 14 extended support after 12 November 2026- End of life
- 12 November 2026
- Released
- Sept 2021
- Final release
- 14.24 (current; one final minor release is due in November 2026)
- Successor
- PostgreSQL 17 or 18 (19 is at release candidate 1)
Date published by PostgreSQL versioning policy. We do not publish a lifecycle date we cannot source. Dates checked on endoflife.date and postgresql.org on 20 October 2026.
Last reviewed
PostgreSQL versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| PostgreSQL 17 | 26 Sept 2024 | 8 November 2029 | Supported |
| PostgreSQL 16 | 14 Sept 2023 | 9 November 2028 | Supported |
| PostgreSQL 15 | 13 Oct 2022 | 11 November 2027 | Approaching |
| PostgreSQL 14 (this page) | 30 Sept 2021 | 12 November 2026 | Approaching |
| PostgreSQL 13 | 24 Sept 2020 | 13 November 2025 | End of life |
| PostgreSQL 12 | 3 Oct 2019 | 21 November 2024 | End of life |
| PostgreSQL 11 | 18 Oct 2018 | 9 November 2023 | End of life |
End-of-life dates are published by each project and checked against endoflife.date.
What actually stops on 12 November 2026
- Quarterly minor releases on the 14 line, after the final November 2026 release.
- Security fixes and, equally important, fixes for data-corruption bugs.
- Community packaging updates for 14 on newer operating systems.
- Engine patches on managed services once their own dates pass. Azure's version policy says that when the community retires a version, Azure stops applying bug and security patches to the database engine, while it keeps patching the host and the service.
What actually breaks in the upgrade
17, 18 or 19
PostgreSQL 19 reached release candidate 1 on 15 October 2026, and postgresql.org plans release candidate 2 for 12 November and general availability for 19 November 2026 (checked 20 October 2026). A new major usually waits for its first minor release before production use, so 17 (supported to November 2029) and 18 (to November 2030) are the safe targets for a move made this autumn. pg_upgrade crosses several majors in one step.
Managed services have their own dates
Amazon RDS for PostgreSQL and Aurora PostgreSQL both list standard support for 14 until 28 February 2027, Extended Support pricing from 1 March 2027, a higher year-three rate from 1 March 2029, and the end of Extended Support on 28 February 2030. Microsoft's extended support page lists Azure standard support for 14 until 31 January 2027 and extended support from 1 February 2027 to 11 November 2029, though its version policy page still shows 11 December 2026 for the standard support end. Check the date that applies to each server.
The date shares a week with .NET 8 and .NET 9
12 November 2026 for PostgreSQL 14 and 10 November 2026 for .NET 8 and 9 land in the same week. Estates running both will have two unrelated upgrade programmes competing for the same change window and the same people. Plan them as one programme or one will slip.
Weeks, not months, are left
A planned upgrade needs an extension audit, a rehearsal and a scheduled window. With the date weeks away, most estates will upgrade the servers that matter most and need cover for the rest. Decide now which servers move before 12 November and which need extended support.
CVEs fixed on PostgreSQL 14 in 2026
The 2026 minor releases fixed 36 CVEs that list PostgreSQL 14 as affected, and PostgreSQL scored 24 of them 7.0 or higher. Every one is fixed in the 14.x minor listed below, so a 14 server on its current minor has them all. A server that stops taking minors does not, which is what happens to every line when it ends.
2026 PostgreSQL security fixes that list 14 as affected
| Released | Fixed in 14 | CVEs fixed | Scored 7.0 or higher |
|---|---|---|---|
| 12 February 2026 | 14.21 | 4 | 3 |
| 14 May 2026 | 14.23 | 8 | 5 |
| 13 August 2026 | 14.24 | 24 | 16 |
Source: the CVE table on postgresql.org/support/security, counted on 20 October 2026. Scores are PostgreSQL's own as the CNA.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to 17 or 18 before November 2026 | Planned pg_upgrade with a rehearsal and a real window. | Depends on extension count, rehearsal time and downtime window | Engineering time | Do this for the servers you can move in time, starting with the most exposed. |
| Amazon RDS or Aurora Extended Support | Standard support for 14 runs to 28 February 2027. From 1 March 2027 instances still on 14 are enrolled in Extended Support unless that was disabled, to 28 February 2030. | None | Charged per vCPU per hour for provisioned instances, on top of the instance, including Multi-AZ standbys, at a higher rate from year three | The default for RDS and Aurora databases that miss the date. The bill grows with instance size. |
| Azure Database for PostgreSQL extended support | Servers still on 14 when Azure standard support ends are enrolled automatically. The only way out is an upgrade. | None | Billed for the time each server runs on the retired version, on top of compute | Covers security and critical fixes only, with no opt-out short of upgrading. |
| OSSeva patched PostgreSQL 14 | Backported security and corruption fixes from the community date, on self-managed servers. | Days to onboard | Subscription | For self-managed servers that cannot move in time, and for estates leaving a managed service. |
| Let the date pass | Unpatched from 13 November 2026. | None | Zero now | Avoidable. This is one of the few version lines with time left to plan. |
What OSSeva does for PostgreSQL 14
OSSeva patches this line
OSSeva backports security and data-corruption fixes to PostgreSQL 14 from the community end-of-life date, as signed packages and container images for self-managed servers, on the Patch, Assure and Operate tiers. If an upgrade to 17 or 18 is the better answer for a server, OSSeva engineers say so and run it.
PostgreSQL extended supportWhat your auditor will say
Nothing changes before the date. From 13 November 2026 requirement 6.3.3 applies the same way it does to any unsupported component.
Auditors increasingly ask for the lifecycle plan before the date rather than the remediation after it. A documented upgrade schedule is itself the evidence.
When does PostgreSQL 14 reach end of life?
12 November 2026, five years after its release on 30 September 2021. The final minor release on the line ships that week.
What is the PostgreSQL 14 end of life date?
12 November 2026 (the PostgreSQL 14 EOL date, also written postgres 14 eol). It is the final release date listed on the postgresql.org versioning policy, checked against endoflife.date on 20 October 2026.
Who sells security patches for PostgreSQL 14 after end of life?
For self-managed servers, OSSeva sells patched, signed 14 builds from 12 November 2026; see PostgreSQL 14 extended support. For RDS and Aurora, AWS sells Extended Support from 1 March 2027, and the RDS Extended Support calculator shows the cost for your vCPU count.
Is PostgreSQL 14 still supported?
Yes, until 12 November 2026. The current minor release is 14.24.
When does PostgreSQL 14 support end on Amazon RDS and Aurora?
Standard support ends on 28 February 2027. RDS Extended Support charges start on 1 March 2027, a higher year-three rate starts on 1 March 2029, and Extended Support ends on 28 February 2030.
When does PostgreSQL 14 support end on Azure?
Microsoft's extended support page lists Azure standard support for 14 until 31 January 2027 and extended support from 1 February 2027 to 11 November 2029. Servers are enrolled automatically and stop being charged only when they are upgraded.
Should I upgrade PostgreSQL 14 to 19?
Not straight away. PostgreSQL 19 was at release candidate 1 on 20 October 2026, with general availability planned for 19 November, a week after 14 ends. For an upgrade before 12 November, 17 or 18 is the safer target.
Should I upgrade PostgreSQL 13 to 14?
No. 14 reaches end of life on 12 November 2026, so it buys very little time. Go to 17 or 18 directly; pg_upgrade crosses multiple majors in a single step.
What happens to PostgreSQL 14 after November 2026?
The community publishes no further minor releases on the line. Security fixes and data-corruption fixes both stop. Managed services carry it a little longer on their own dates, and third-party extended support covers self-managed servers.
Get a quote
Still running PostgreSQL 14?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.
Prefer to talk or read more first?