PostgreSQL 14 has reached end of life: a fleet check across 14 measured databases
PostgreSQL 14 went out of support on November 12, 2026. The project's version table lists that date as the final release, and the announcement of the same day says so in plain words: "This is the final release of PostgreSQL 14." The last release is 14.25. That raised a question about our own setup: which databases actually run here, and does one of them sit on a line with no future? A read-only pass over twelve reachable hosts found fourteen databases, thirteen on PostgreSQL 17 and one on 14.19. A fifteenth is listed in the inventory, but its host was unreachable. A note on scope: this is the result of the method “ask each host with docker exec or psql”. Our process census of the same day counts by process and reaches different numbers (25 instances on 19 machines, two of them on major 14: 14.24 and 14.19). The 14.24 instance runs in rootless Podman and is invisible to docker exec; this fleet check has a coverage gap there. Different method, different number.
End of life at PostgreSQL means this: a major version gets updates for five years after its first release, then one last minor release ships, and after that there are no bug fixes and no security fixes. It does not matter who ships the binary, be it a distribution, a vendor or a container image. Whatever is found in version 14 after November 12, 2026 stays unfixed.
What the version table shows
The table on the versioning policy page is the only date that counts. Retrieved on November 15, 2026, after the release of November 12:
| Major | First release | Current minor | Support ends |
|---|---|---|---|
| 18 | September 25, 2025 | 18.7 | November 14, 2030 |
| 17 | September 26, 2024 | 17.12 | November 8, 2029 |
| 16 | September 14, 2023 | 16.16 | November 9, 2028 |
| 15 | October 13, 2022 | 15.20 | November 11, 2027 |
| 14 | September 30, 2021 | 14.25 | November 12, 2026, passed |
| 13 | September 24, 2020 | 13.23 | November 13, 2025, passed |
Every major lives five years, all end dates fall between November 8 and 14, and minor releases ship for every supported line on the same day. Version 15 has just under a year left, until November 2027, and 17 has just under three. Version 19 is next: the announcement of November 12 includes 19 RC 2 and names November 19, 2026 as the planned release date.
What the last two waves closed for 14
According to its announcement, the release of November 12 fixes 52 security vulnerabilities across all supported lines. The project's security page for version 14 lists 40 of them with a fix in 14.25, 29 rated CVSS 8.0 or higher. Most are memory errors or type confusions in the server and in the PL/Perl, PL/Tcl and PL/pgSQL languages that can lead to code execution. Two client tools are affected as well: CVE-2026-116330 (pg_dump, tar archive and psql commands) and CVE-2026-116314 (pg_restore executes code), both at CVSS 8.8.
The August release 14.24 carried 24 entries, 15 of them at CVSS 8.0 or higher. They include heap overflows in the regular expression code (CVE-2026-14664), in to_char (CVE-2026-14669), in PL/Perl (CVE-2026-14670) and in pg_dump (CVE-2026-19385). CVE-2026-18408 is a different case and hits psql: the superuser of a source server can run code in the psql client through \unrestrict.
On how patches arrive: the project is a CVE Numbering Authority itself, with Red Hat as CNA Root, and ships security fixes through minor releases. A minor update is a restart with swapped binaries and needs no dump. The versioning policy says the community considers minor upgrades less risky than continuing to run an old minor. A major upgrade is different, and for version 14 it is now the only way forward. The 14.25 announcement also lists GIN, pg_trgm GiST and bpchar index corrections that require a reindex after the update. It lists them under PostgreSQL 18 and says many of them affect other supported lines too; which ones apply to 14 is a question for the release notes.
The fleet check: method and result
We measured on November 12, 2026, read-only, with two tools: docker exec <name> postgres --version inside containers and show server_version over psql on host installs. We asked the programs on purpose, because an image tag only states an intention. Result: twelve hosts reachable, fourteen databases measured, one host in the inventory unreachable and its state open. We queried the two photo-platform rows again on November 15, 2026 at 16:47 (SSH via an intermediate host, docker exec into the application's database containers): still 17.8 and 14.19. Instances that do not run under Docker are reached by this method only through psql on the host; rootless Podman without a Docker client not at all.
| Instance by role | Measured version | Platform | Method | Measured on |
|---|---|---|---|---|
| 2 mail gateways | 17.11 | host install (pgdg) | show server_version | November 12, 2026 |
| 2 identity services | 17.11 | container postgres:17 | postgres --version | November 12, 2026 |
| Archive and log databases (3) | 17.11 | container postgres:17 | postgres --version | November 12, 2026 |
| Operations and analytics databases (4) | 17.11 | container postgres:17 | postgres --version | November 12, 2026 |
| Ticket system | 17.9 | container postgres:17.9 | postgres --version | November 12, 2026 |
| Photo platform, newly built | 17.8 | container pg17 image | postgres --version | November 12, 2026 |
| Photo platform, legacy | 14.19 | container pg14 image | postgres --version | November 12, 2026 |
| One further host | not reachable | inventory lists a database | measurement open | November 12, 2026 |
The numbers are the programs' own output, not the image tag. Since November 12 there is 17.12, so the thirteen 17 instances are one to four minor steps behind. That can be caught up in the next maintenance window. The single 14 is the finding of this method; the process census found the 14.24 in rootless Podman on top.
How the 14 got there and why it stayed
The old instance is the database of a photo platform, shipped as a pinned container image by the application project and built back when the platform ran its previous version. The sister system of the same application, rebuilt later, runs on that project's current pg17 image. The application is the same on both. Someone fixed an image tag once, and nobody has swapped the image since. A pinned tag does not change with any docker pull, so the database stayed on 14.19. Up to 14.25 that is six minor releases and 78 security entries for the 14 line (14.22 had none), 51 of them at CVSS 8.0 or higher.
The Postgres container publishes no port on the host (docker ps on November 15, 2026: only 5432/tcp internally), and the application in front of it is reachable through an internal proxy. The practical exposure is small. The exit is due anyway, and the application brings its own path: full dump, new instance on the project's current pg17 image, restore, comparison. With the vector search, the index extensions ship inside that very image, which ties the major upgrade to the image swap here. A similar case with a hard date is described in Proxmox VE 8: support ends in August; the next version is covered in PostgreSQL 19 RC1: JIT and LZ4.
What to do now, in this order
- Inventory first: list every instance, including those that only exist in an inventory, and every container with a pinned tag. The unreachable host in our table is exactly that gap.
- Measure the actual state: version inside the container or via show server_version, and write down the date and the method.
- Rank by risk: public entry point or not, backup in place or not, exit path of the application known or not.
- Treat the major upgrade as a project: dump, new instance, restore, compare object counts, test the application. The PostgreSQL upgrade documentation describes dump/reload and pg_upgrade; for application containers, the application team's documentation decides.
- Take care of the next date in the same pass: version 15 ends on November 11, 2027.
If you would rather not run the exit alone during live operations, our IT infrastructure and operations service starts with exactly this inventory. More on keeping versions current is in the topic area Servers and network.
Open points: The 14.24 instance in rootless Podman is not in the table below (a coverage gap of this method, see the process census). The fleet table (twelve hosts, fourteen databases) dates from November 12, 2026, and only the two photo-platform rows were measured again on November 15. One inventory host was unreachable and its version is unknown. The "current minor" column and the CVE counts were taken from the project's pages on November 15 or counted by us; a later release changes them.
Read next: PostgreSQL 14: our process census · OpenVDDK as a stand-in for VMware's VDDK · SSD, HDD and RAM prices in November
Further Reading
Each source is marked with what it supports: verified = retrieved and read by us on November 15, 2026, derived = calculated by us from it.
- PostgreSQL Versioning Policy, verified November 15, 2026: version table, end dates, rule on minor updates. The remaining-years chart is derived.
- PostgreSQL Security Information, verified November 15, 2026: CNA status with Red Hat as CNA Root.
- Security overview for PostgreSQL 14, verified November 15, 2026: we counted 40 and 29 (14.25), 24 and 15 (14.24) and 78 and 51 (14.20 to 14.25) from the table ourselves, derived.
- Release announcement 18.7, 17.12, 16.16, 15.20, 14.25 and 19 RC 2, verified, November 12, 2026: 52 security fixes, end-of-life notice for 14, reindex notes, planned date November 19, 2026 (vendor statement).
- Release announcement 18.6, 17.11, 16.15, 15.19, 14.24 and 19 Beta 3, verified, August 13, 2026.
- PostgreSQL 14: Upgrading a PostgreSQL Cluster, verified November 15, 2026: dump/reload and pg_upgrade.
- Own measurement: versions via
docker exec <name> postgres --versionandshow server_version, November 12, 2026, read-only; photo platform again on November 15, 2026 at 16:47.
Is PostgreSQL 14 unsafe now that support has ended?+
Not overnight, but the gap grows from here. 14.25 of November 12, 2026 closed 40 vulnerabilities in this line, 29 of them rated CVSS 8.0 or higher. Anything found in 14 after that date gets no patch, whether it runs from a distribution or a container image. A server still on an older 14 minor is also missing the fixes of every release in between.
How do I check a database that runs in a container?+
Read the version from the running container; the image tag only states an intention. docker exec with postgres --version returns what actually runs, and on a host install show server_version over psql gives the same number. A pinned image tag does not move with any docker pull.
Does every PostgreSQL 14 instance have to be shut down right away?+
No, the order follows the risk. An instance with no public entry point and a working backup can wait for a plan that takes weeks. An instance that takes logins from the network needs a migration plan now. The exit path is the same in both cases: full dump, new instance on a supported version, restore, comparison.
senn-tech