Key details

  1. Released 12 November 2026: PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25 and 19 RC2.
  2. Upstream reports 52 CVE fixes and over 140 other bug fixes.
  3. CVE-2026-6460 and several other issues carry CVSS 8.8; exploit prerequisites vary.
  4. PostgreSQL 14.25 is the final community-supported version 14 release.
  5. Post-upgrade REINDEX and fresh full backup steps may be necessary depending on exposure.

What builders should take away

  1. Inventory exact PostgreSQL server versions and extensions; prioritise supported-line security updates.
  2. Use the upstream security index to assess exposure by CVE, privilege and version, not headline CVE count.
  3. Read the Updating section before upgrading; identify affected indexes and incremental backups.
  4. Take and test backups and plan PostgreSQL 14 major-version migrations now.

What changed

On 12 November 2026 the PostgreSQL Global Development Group released versions 18.7, 17.12, 16.16, 15.20 and 14.25, plus PostgreSQL 19 RC2. The supported-line maintenance releases address 52 security vulnerabilities and more than 140 bugs. PostgreSQL 14.25 is the last community-supported PostgreSQL 14 release; PostgreSQL 19 general availability is scheduled for 19 November, not yet released.

Why it matters

The release combines high-severity code-execution and privilege-boundary defects with correctness problems involving indexes, backups, replication and query results. Operators cannot assume that installing patched binaries alone repairs indexes previously affected by corruption or restores trust in an existing incremental backup chain. Teams still running PostgreSQL 14 need a major-version migration plan because subsequent community security fixes will not be backported to that line.

Affected versions and representative security issues

The upstream security list includes CVE-2026-6460, a type-confusion arbitrary-code-execution issue rated CVSS 8.8; CVE-2026-6467, an extension-script schema-handling issue rated 7.2; CVE-2026-14661, involving arbitrary-file append through dblink and subscriptions (8.1); and CVE-2026-116318, involving SQL injection through pg_dump constraint names (8.8). Each CVE has distinct privileges, entry points and affected-version boundaries; the count of 52 must not be interpreted as 52 unauthenticated remotely exploitable flaws. The official PostgreSQL security index supplies version-by-version details.

Upgrade steps and repairs beyond binaries

PostgreSQL says minor upgrades normally require stopping the server and replacing binaries, not dump/reload or pg_upgrade. But operators should inspect the release's Updating section: suspect GIN and pg_trgm GiST indexes may need REINDEX, as may TOAST indexes affected by missing-chunk failures and indexes on lengthless bpchar columns. For incremental backups, the project recommends taking a fresh full backup after updating before resuming the incremental chain. Certain partition constraints require inspection and repair. Operators who skipped earlier maintenance releases must review intervening upgrade notes too.

PostgreSQL 14 support ends

PostgreSQL 14.25 is the final community release for major version 14. Its end of support is distinct from the availability of the 14.25 patch: applying that patch closes known issues now but does not deliver future community fixes. A move to a supported major line needs pg_upgrade or a dump/restore migration, application and extension compatibility testing, and a rollback plan. Vendor-specific extended-support products are separate from community support and must be verified individually.

What PostgreSQL 19 RC2 does not mean

PostgreSQL 19 RC2 contains applicable fixes but remains a release candidate as of 14 November. Its planned 19 November general availability is not a reason to delay security maintenance of production 15–18 clusters. Evaluate RC-specific changes in test environments only.

What to watch next

  • Vendor and distribution security backports and managed-service deployment timing.
  • Any confirmed exploitation reports or corrected CVE affected-version details.
  • PostgreSQL 19 general availability, currently planned for 19 November.

Still unclear

  • No confirmed exploitation of the listed issues was established in this pass.
  • Managed database vendor patch rollout dates and distro-specific packages were not independently verified.
  • Whether reindexing is necessary depends on the operator's actual index types and prior corruption exposure.

Sources

Direct reading behind this dossier.

3 sources

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment