PostgreSQL 15 end of life
PostgreSQL 15 is supported by the PostgreSQL Global Development Group until 11 November 2027, five years after its first release on 13 October 2022. The current minor release is 15.20, and 15.x keeps receiving fixes until that date. After it, the community stops patching 15. OSSeva supports PostgreSQL 15 now and ships patched 15 builds past November 2027.
What now
Which vendors provide PostgreSQL 15 security patches after 11 November 2027?
PostgreSQL 14 extended support after 12 November 2026- End of life
- 11 November 2027
- Released
- Oct 2022
- Final release
- 15.20 (current minor)
- Successor
- PostgreSQL 17 or 18
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 (this page) | 13 Oct 2022 | 11 November 2027 | Approaching |
| PostgreSQL 14 | 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 11 November 2027
- Minor releases on the 15.x line after 11 November 2027.
- Security fixes for the server and the bundled client tools.
- Fixes for data-corruption and crash bugs, which make up much of each minor release.
What actually breaks in the upgrade
Pick the target by its date
The community supports PostgreSQL 16 until 9 November 2028, 17 until 8 November 2029 and 18 until 14 November 2030. A move from 15 to 16 buys one year.
PostgreSQL 18 turns checksums on by default
initdb in PostgreSQL 18 enables data checksums by default, and pg_upgrade requires matching checksum settings. A 15 cluster created without checksums needs the new cluster initialised with --no-data-checksums, or a dump and restore.
Estates on 14 go first
PostgreSQL 14 reaches end of life on 12 November 2026. Where both lines run, 14 sets the first deadline and 15 the second, a year later.
CVEs fixed on PostgreSQL 15 in 2026
The 2026 minor releases fixed 77 CVEs that list PostgreSQL 15 as affected, and PostgreSQL scored 55 of them 7.0 or higher. Every one is fixed in the 15.x minor listed below, so a 15 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 15 as affected
| Released | Fixed in 15 | CVEs fixed | Scored 7.0 or higher |
|---|---|---|---|
| 12 February 2026 | 15.16 | 4 | 3 |
| 14 May 2026 | 15.18 | 8 | 5 |
| 13 August 2026 | 15.19 | 24 | 16 |
| 12 November 2026 | 15.20 | 41 | 31 |
Source: the CVE table on postgresql.org/support/security, counted on 14 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 PostgreSQL 17 or 18 | pg_upgrade or logical replication to a newer major. | Depends on extension count, rehearsal time and downtime window | Engineering time | The destination. 18 has the longest runway. |
| Managed cloud extended support | Paid extended support on some managed services after community end of life. | None | Per-vCPU surcharge | Only for managed instances, and on RDS the surcharge doubles in year three. |
| OSSeva on PostgreSQL 15 | Support now, and signed patched 15 builds after November 2027. | Days | Subscription | Takes the date off the migration plan for self-managed clusters. |
What OSSeva does for PostgreSQL 15
OSSeva patches this line
OSSeva covers PostgreSQL 15 today on the Assure and Operate tiers, and Patch subscriptions continue signed, backported fixes on 15 after 11 November 2027, with no change of supplier when community support stops.
PostgreSQL extended supportWhat your auditor will say
The data store is a system component in its own right. An unsupported version with no patch source is a finding; a documented third-party patch stream is the usual remediation.
For EU financial entities, the ICT risk and third-party provisions apply when a critical service depends on software with no support arrangement in place.
When does PostgreSQL 15 reach end of life?
On 11 November 2027, five years after its first release on 13 October 2022.
What is the latest PostgreSQL 15 release?
15.20 is the current minor release on postgresql.org. Minor releases continue until 11 November 2027.
Should I upgrade from PostgreSQL 15 to 16, 17 or 18?
17 or 18. PostgreSQL 16 ends on 9 November 2028, 17 on 8 November 2029 and 18 on 14 November 2030.
Can I keep PostgreSQL 15 patched after November 2027?
Yes. OSSeva supports PostgreSQL 15 today and ships patched 15 builds after the community end-of-life date.
Get a quote
Still running PostgreSQL 15?
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?