PostgreSQL 14 EOL: End of Life Was 12 November 2026
PostgreSQL 14 EOL was 12 November 2026, five years after its 30 September 2021 release. The final minor release is 14.25, and the community ships no further security or data-corruption fixes. Upgrade to 17 or 18, or keep self-managed 14 patched with OSSeva. RDS and Aurora standard support runs to 28 February 2027.
Who patches PostgreSQL 14 after its end date?
OSSeva patches PostgreSQL 14 after its end date under its patch SLA: Critical fixes within 48 hours and High within 7 days.
Check if my version is coveredWhat now
Which vendors provide PostgreSQL 14 security patches now that support has ended?
PostgreSQL 14 extended support after 12 November 2026- End of life
- 12 November 2026
- Released
- Sept 2021
- Final release
- 14.25 (final, 12 November 2026)
- Successor
- PostgreSQL 17 or 18 (19 is planned for 19 November 2026)
Date published by PostgreSQL versioning policy. We do not publish a lifecycle date we cannot source. Dates checked against the postgresql.org versioning policy, the 14.25 release notes and endoflife.date, and against the Amazon RDS release calendar, the Microsoft Azure extended support page and the Google Cloud SQL version policy, on 17 November 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 | End of life |
| 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. The final one is the last the community publishes.
- 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 2 on 12 November 2026 (release candidate 1 was 15 October 2026) and had not reached general availability when checked on 12 November 2026; postgresql.org plans it for 19 November 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 now, whatever 19's status. pg_upgrade crosses several majors in one step. The 17 dates are on PostgreSQL 17 end of life (8 November 2029).
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. 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 fell in the same week. Estates running both now have two unrelated upgrade programmes competing for the same change window and the same people. Plan them as one programme or one will slip.
The date has passed
The community shipped 14.25 on 12 November 2026, the final 14.x release, with fixes for 40 CVEs, including CVE-2026-6460, CVE-2026-18447 and CVE-2026-116304 (each scored 8.8). Its release notes call it the last expected 14.x release and warn that several bugs could cause index corruption, so reindex any index the changelog says may be affected. A planned upgrade needs an extension audit, a rehearsal and a scheduled window. Servers still on 14 now need a dated plan and cover, because the next advisory has no community fix on this line. Decide which servers move first and which need extended support in the meantime.
PostgreSQL 14 end of life dates at a glance
PostgreSQL 14 end of life was 12 November 2026, when the community shipped 14.25, the final 14.x release. The managed services run later: Amazon RDS and Aurora to 28 February 2027, Azure to 31 January 2027, then paid Extended Support on both.
PostgreSQL 14 support dates by where it runs
| Where 14 runs | Standard or community support ends | Paid Extended Support |
|---|---|---|
| Self-managed (postgresql.org) | 12 November 2026, final release 14.25 | None from the community; OSSeva ships patched, signed 14 builds |
| Amazon RDS and Aurora PostgreSQL | 28 February 2027 | From 1 March 2027 to 28 February 2030, at a higher rate from 1 March 2029 |
| Azure Database for PostgreSQL Flexible Server | 31 January 2027 | 1 February 2027 to 11 November 2029 |
| Google Cloud SQL for PostgreSQL | Extended support starts 1 February 2027 | To 1 February 2030, when 14 is deprecated and upgraded |
| Upgrade targets | PostgreSQL 17 ends 8 November 2029; 18 ends 14 November 2030 | Not needed |
Sources: the postgresql.org versioning policy and the 14.25 release notes, the Amazon RDS for PostgreSQL release calendar, Microsoft's Azure extended support page and Google's Cloud SQL version policy, read 17 November 2026.
CVEs fixed on PostgreSQL 14 in 2026
The 2026 minor releases fixed 76 CVEs that list PostgreSQL 14 as affected, and PostgreSQL scored 55 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 |
| 12 November 2026 | 14.25 | 40 | 31 |
Source: the CVE table on postgresql.org/support/security, recounted on 17 November 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 | Planned pg_upgrade with a rehearsal and a real window. | Depends on extension count, rehearsal time and downtime window | Engineering time | Do this for every server you can move, 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. |
| Stay on the final release unpatched | No community fixes since 12 November 2026. | None | Zero now | Hard to defend: any CVE disclosed from here has no community fix on 14. |
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
From 13 November 2026, requirement 6.3.3 applies to PostgreSQL 14 the same way it does to any unsupported component.
Auditors now ask for the remediation after the date. A documented, dated upgrade schedule, or a named patch source for each 14 server, is the evidence.
When did 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, 14.25, shipped on 12 November 2026.
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 12 November 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?
No. Community support ended on 12 November 2026. The final release is 14.25.
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. A new major usually waits for its first minor release before production use, and PostgreSQL 19 reached release candidate 2 on 12 November 2026 (release candidate 1 was 15 October 2026) and had not reached general availability when checked on 12 November 2026; postgresql.org plans it for 19 November 2026. For an upgrade now, 17 or 18 is the safer target.
Should I upgrade PostgreSQL 13 to 14?
No. 14 reached end of life on 12 November 2026, so it buys no time. Go to 17 or 18 directly; pg_upgrade crosses multiple majors in a single step.
What is in PostgreSQL 14.25, the last 14 release?
14.25 shipped on 12 November 2026 with fixes for 40 CVEs that list 14 as affected. Its release notes say it is expected to be the last 14.x release and tell users to reindex any index that the corruption bugs in the changelog may have touched. Update every 14 server to 14.25 first, then plan the move.
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?