Security advisory: PostgreSQL: 52 vulnerabilities, including code execution

Published: November 17, 2026

CVE-2026-6460 and 51 others | Fixed in 18.7, 17.12, 16.16, 15.20 and 14.25

Severity: High (CVSS 8.8)

Status: Patch available — update now

PostgreSQL 14 reached end of life with this release. 14.25 is the last update it will receive.

Topics on this page:

Summary

On November 12, the PostgreSQL Global Development Group released 18.7, 17.12, 16.16, 15.20 and 14.25, fixing 52 security vulnerabilities and more than 140 other bugs across every supported version. The most serious, CVE-2026-6460, lets a database user who can create objects run arbitrary code on the server as the operating system account that runs PostgreSQL. About 20 other flaws in the core server lead to the same result.

Almost all 52 require a database login, but that is a low bar. Student and research accounts on shared servers, application credentials and any web application with a SQL injection flaw can all be leveraged to gain this access. Code running as the PostgreSQL service account can read or change every database on that server, whatever permissions were granted inside PostgreSQL. There is no workaround; updating is the only fix.

The planning point: start with servers where anyone other than the DBAs can log in: shared teaching and research servers, multi-tenant systems, and databases behind web applications. Update the client tools on admin workstations and backup systems as well, since six of the flaws are in pg_dump, pg_restore and related utilities rather than the server.

Vulnerability details

Field Detail
CVE-2026-6460 Type confusion after ALTER … SET DATA TYPE and other DDL. A user who can create objects runs code as the OS account that owns the database process. The temporary-object privilege every role has by default may be enough. CVSS 8.8.
Other code execution About 20 further type-confusion, use-after-free and buffer-overflow flaws in the core server, nearly all rated 8.8 and reachable through ordinary SQL, including PL/pgSQL, which is installed by default.
Optional components PL/Perl (five CVEs), PL/Tcl, dblink, foreign data wrappers and logical replication. A subscriber replicating from a publisher an attacker controls can be compromised without any login on the subscriber.
Access control bypass Several flaws let a user read or change rows despite row-level security policies, a view’s WHERE condition or a security_barrier view. They score lower but matter wherever RLS separates users or tenants.
Client tools Crafted archives or a dump of a hostile database can run code on the machine doing the restore (pg_restore, pg_dump). reindexdb, vacuumdb and pg_basebackup are also affected.
Severity High. Most of the 52 are rated High; the top score is CVSS v3.1 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
Exploit status No confirmed exploitation in the wild has been reported. A credited researcher has published a detailed technical write-up of CVE-2026-6460, so assume working exploits are available or will be soon.

Impacted and fixed versions

PostgreSQL version Status Fixed in / Action
18, 17, 16, 15 Vulnerable before 18.7, 17.12, 16.16 and 15.20 Update to 18.7, 17.12, 16.16 or 15.20
14 Vulnerable before 14.25. End of life as of November 12, 2026. Update to 14.25 now, then plan the upgrade to a supported major version.
13 and older Vulnerable. End of life; no fix. Upgrade to a supported version, or restrict access to trusted administrators until you do.
19 (pre-release) RC 2 includes the fixes. General availability planned for November 19. Use the GA release for new deployments.
Distribution, container and managed services Fixed on each vendor’s schedule. Check your Linux distribution, container image or cloud provider. Products that bundle PostgreSQL need the vendor’s update.

Recommendations

  • Update the server. These patches are a minor release: stop PostgreSQL, replace the binaries and restart. No dump and reload or pg_upgrade is needed. Start with shared, multi-user and application-facing servers.
  • Confirm the running version. After the restart, run SHOW server_version; on every instance, including replicas and standbys.
  • Rebuild C-language extensions. PostgreSQL says full protection against CVE-2026-6460 requires rebuilding C-language extensions, and some will need source changes. For packaged extensions, confirm the package was rebuilt for the new release. Leave the new composite_type_mismatch setting at its default; PostgreSQL warns that disabling its checks carries security risks.
  • Update client tools everywhere. Update pg_dump, pg_restore and psql on admin workstations, backup servers, CI pipelines and container images. Do not restore dumps from untrusted sources with unpatched tools.
  • Complete the post-update steps. This release also fixes index corruption and backup bugs. Reindex pg_trgm GiST indexes (gist_trgm_ops) and B-tree indexes on bpchar columns declared without a length, reindex any GIN index you suspect is corrupt, and take a new full backup if you use incremental backups. The release announcement’s Updating section has the details.
  • Until you can update, narrow who can log in. Doing this reduces exposure but does not fix anything. Remove login roles that are not needed, restrict pg_hba.conf to the hosts and networks that need access, keep port 5432 off the internet, and drop unused languages and extensions such as plperl, pltcl and dblink.
  • Plan the move off PostgreSQL 14 and older. The next PostgreSQL security release will not include 14.

Detection & verification

Successful exploitation runs code as the PostgreSQL service account, so check the host as well as the database logs.

  • Backend crashes. Memory-corruption attempts often crash a backend before they succeed. Look for terminated by signal 11 or other abnormal backend exits followed by crash recovery in the PostgreSQL logs, especially when repeated or tied to one role.
  • Unusual DDL from low-privileged roles. Where log_statement = ‘ddl’ is set, look for ALTER … TYPE, CREATE TYPE, CREATE FUNCTION or CREATE AGGREGATE from application or user accounts that do not normally change the schema.
  • Activity by the service account. PostgreSQL processes launching shells, interpreters or download tools, outbound connections from the database host, and new files, cron jobs or scheduled tasks owned by the postgres account.

Support

As always, please let us know if you have any questions or concerns or see unusual activity on your systems that you believe might be associated with this or any other vulnerability. Please send these communications to security.response@utoronto.ca.