PostgreSQL 14.25 came out on November 12, 2026 and, according to the release notes, is expected to be the last release in the 14 branch. Versions 18.7, 17.12, 16.16 and 15.20 shipped the same day. Release 14.25 fixes 41 vulnerabilities with CVEs and a group of bugs that can corrupt indexes. For some of them, updating is not enough: the project asks users to rebuild the affected indexes with REINDEX.
What went into the last 14.x release
Most of the security fixes deal with use-after-free, buffer overruns and type violations that a user with database access can trigger with crafted SQL. Two of them change visible behavior:
INSERT ... ON CONFLICT DO UPDATEon a view could update rows hidden by the view'sWHEREclause. The command now raises an error in that case (CVE-2026-16237).- The fix for concurrent changes to composite types (CVE-2026-6460) adds version checks on stored data. According to the notes, full protection requires rebuilding C-language extensions, and some will need source code changes. A new parameter,
composite_type_mismatch, can turn the check off, and the project itself warns that doing so carries security risks.
The index bugs are a separate group, and they are where the work after the update lies:
- btree indexes on
bpcharcolumns declared without a length can return wrong results in index-only scans. The fix covers new entries; existing ones needREINDEX.CHAR(n)columns, with a length, are not affected; - GiST indexes using
gist_trgm_ops(frompg_trgm, used for fuzzy text search) could miss matching rows. The notes say to rebuild them too; - two defects in GIN indexes, one in
VACUUMand one in page deletion, could leave entries pointing at the wrong rows or make searches miss rows. HereREINDEXis recommended if you suspect corruption; - indexes on TOAST tables (where PostgreSQL stores large values) could lose entries after
REINDEX CONCURRENTLY, with "missing chunk number" errors. The data itself is intact and aREINDEXfixes it.
The same index fixes and the composite type change appear in the 18.7 notes, so the rebuild work applies to every supported branch.
Who needs to act
Any application on PostgreSQL 15 through 18 needs the minor update and a check of the indexes listed above. Teams that use pg_trgm for site or store search, JSONB or text columns with GIN indexes, or C extensions outside the standard package have more to review.
Teams still on 14 have a bigger problem. After 14.25, new bugs will not be fixed in that branch. This weighs most on databases running on self-managed servers or pinned Docker images, and on older systems nobody upgraded because they "were working". On a managed database, the end of upstream support does not switch anything off on the same day, but it moves the decision to the provider's calendar and price list.
What to do now
First, update to the minor release for your branch (18.7, 17.12, 16.16, 15.20 or 14.25). The notes say no dump and restore is needed. Then list btree indexes on bpchar columns and gist_trgm_ops indexes and rebuild them; for the GIN and TOAST cases, check for symptoms before rebuilding everything. REINDEX CONCURRENTLY avoids blocking writes on large tables, at the cost of more time and more disk space during the operation. If the database uses C extensions built by your team or by third parties, confirm with whoever maintains each one that a rebuilt version exists for the new minor release.
For teams on 14, updating to 14.25 closes the bugs known today, and moving to a supported branch now has a real deadline. A new major version usually means testing the application, the extensions and the backup process. I wrote about that trade-off in A supported version still calls for a migration decision: the cost of postponing grows while the system looks stable.
What is still unknown
The notes do not say whether any of the bugs were exploited. They also do not say when each managed provider will roll out the new versions or how long it will keep the 14 branch after upstream support ends; that has to be checked in each provider's console and documentation. Finally, the PostgreSQL 19 release notes in the repository list November 19 as the release date, which may change the target for anyone planning the move off 14 now.
If your company is weighing something similar, reach me on LinkedIn or WhatsApp.