Decoding the world of cybersecurity

PostgreSQL fixes 52 vulnerabilities as version 14 support ends

PostgreSQL administrators face extensive security fixes and an unsupported branch. The latest maintenance releases address 52 vulnerabilities and more than 140 bugs, while version 14 reaches end of life.

PostgreSQL fixes 52 vulnerabilities as version 14 support ends
Summary
  • PostgreSQL released fixes for 52 vulnerabilities on 12 November, covering code execution, privilege enforcement and information disclosure.
  • PostgreSQL 14.25 is the final release of version 14, which no longer receives security or bug fixes.
  • Several unrelated index and backup bugs may require reindexing or a new full backup after updating, beyond replacing database binaries.

PostgreSQL has released security corrections for 52 vulnerabilities across its supported database branches, alongside more than 140 bug fixes, as organisations running version 14 face the end of its security support.

The PostgreSQL Global Development Group issued versions 18.7, 17.12, 16.16, 15.20 and 14.25 on 12 November. The project also published a second release candidate for PostgreSQL 19, which remains pre-release software rather than a production maintenance update.

The security fixes address weaknesses involving memory handling, database permissions, extension processing, backup utilities and other components. Some can permit arbitrary code execution under particular conditions, while others may expose information or undermine restrictions intended to control access to database contents.

Version 14.25 is the final update for PostgreSQL 14. The project has ended that branch’s support, meaning future security and reliability corrections will not be issued for installations that remain on the older major version.

Security flaws affect different database functions

The 52 vulnerabilities cover a wide range of mechanisms and prerequisites. Several involve type confusion or memory safety errors, while others affect permission checks, utility programs or functions that interact with external systems.

CVE-2026-6460, rated 8.8 under CVSS version 3.1, concerns a type confusion error associated with changing column data types. The project says exploitation can permit arbitrary code execution under affected conditions.

Another vulnerability, CVE-2026-14661, concerns circumstances in which the dblink extension and subscriptions can append information to arbitrary files. It has a severity score of 8.1.

The update also addresses a weakness involving logical replication, CVE-2026-120145, where changes applied to a subscriber’s system catalogues could lead to code execution.

Other security fixes concern database backup and restore utilities. Vulnerabilities in pg_restore, pg_dump and reindexdb can expose execution or injection risks when those tools process particular kinds of malicious or inadequately validated input.

Not every vulnerability is remotely exploitable or available to an unauthenticated attacker. Database permissions, installed extensions and the ability to control relevant queries or input determine whether an individual weakness can be reached.

The difference is particularly important in shared database environments, where applications and service accounts may have different privileges. A vulnerability requiring an existing database role presents a different exposure from one reachable before authentication.

The PostgreSQL project has not claimed in its release announcement that all 52 vulnerabilities were being actively exploited. Severity ratings and technical descriptions provide a basis for assessing exposure, but they do not establish the same risk across every deployment.

PostgreSQL 14 reaches the end of its lifecycle

Although PostgreSQL 14.25 contains the final security corrections for its branch, installing it does not extend the product’s supported lifecycle.

The project follows a major-version support policy under which older releases eventually stop receiving fixes. Organisations still operating PostgreSQL 14 must therefore plan migration to a supported major version rather than relying on further maintenance releases.

Moving between minor releases within the same branch is generally less disruptive. PostgreSQL says the November maintenance updates are cumulative and can ordinarily be applied by stopping the database service and updating the installed binaries, without dumping and reloading the entire database.

A major-version migration requires a separate process. Depending on the installation, this may involve pg_upgrade, logical replication or another supported method for transferring database contents and associated configuration.

Applications may also depend on extensions, drivers or database functions whose compatibility needs to be assessed before a major upgrade. Production migrations can therefore require application testing, planned interruptions and procedures for restoring service if an upgrade cannot be completed successfully.

The distinction leaves database administrators with two tasks. Current supported installations need the November security corrections, while systems remaining on PostgreSQL 14 require a longer-term transition away from unsupported software.

Index and backup problems require additional checks

The maintenance release also corrects database integrity problems that are separate from the 52 published security vulnerabilities.

Several bugs affected Generalized Inverted Indexes (GIN), potentially causing queries to miss matching records or return unrelated results. The project advises administrators to reindex affected structures where corruption is suspected.

A separate issue involving GiST indexes using pg_trgm could also produce incorrect search results. PostgreSQL recommends rebuilding those indexes after installing the update.

Other corrections concern B-tree indexes involving columns declared as bpchar without a length, along with certain TOAST-table operations. The release guidance identifies circumstances in which reindexing remains necessary because replacing the software does not repair previously corrupted index data.

Incremental backups require particular attention. PostgreSQL identified several bugs that could cause corrupted backup copies and recommends taking a new full backup after updating where incremental backups are used.

Further fixes address problems involving standby servers, transaction handling and query planning, including circumstances in which databases could return incorrect results or lose consistency after a crash.

These issues introduce requirements beyond ordinary vulnerability remediation. A database can run updated binaries while retaining damaged indexes or relying on backups created before the relevant reliability problems were corrected.

The project has therefore published specific post-update procedures for affected installations. The appropriate actions depend on the database features in use and whether the organisation has encountered the conditions described in the release notes.

Managed database services may deploy corrections through provider-controlled maintenance windows, while organisations operating their own servers remain responsible for planning installation, checking affected indexes and validating recovery arrangements.

PostgreSQL’s 12 November update provides security and reliability fixes for its supported branches. For installations still using PostgreSQL 14, version 14.25 is the last available correction from the project, and the next major-version upgrade must take place without the prospect of further fixes for that branch.

×