Mastodon Mastodon Mastodon Mastodon

PostgreSQL fixes 52 vulnerabilities, including type confusion with code execution on the server

Photo of author

CyberSecureFox Editorial Team

Published:

On 12 November 2026, the PostgreSQL Global Development Group released minor updates for all supported branches, fixing 52 security vulnerabilities and more than 140 bugs. The central vulnerability of the release — CVE-2026-6460 (CVSS 8.8) — allows an authenticated user with object-creation privileges to execute arbitrary code as the system account under which PostgreSQL runs. All versions prior to 18.7, 17.12, 16.16, 15.20 and 14.25 are vulnerable. Full protection requires not only updating the server, but also rebuilding all C extensions. Exploitation in the wild has not been observed, but a public PoC exploit is already available.

Technical essence of CVE-2026-6460

The vulnerability belongs to the CWE-843 class (type confusion — accessing a resource with an incompatible type), according to Red Hat’s assessment. The issue is related to composite types — structures consisting of named fields with their own data types. When changing a field’s type via DDL operations (for example, ALTER ... SET DATA TYPE), the server could continue to interpret previously stored values according to the new type layout, which led to type confusion.

According to the project’s official advisory, an attacker must be able to create objects in the database. The attack vector is network-based, with no need for user interaction (CVSS vector: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Successful exploitation gives full control over the host at the privilege level of the PostgreSQL process.

Researcher Mehmet Ince published a technical write-up of a working exploit demonstrated on PostgreSQL 18.6. According to him, the exploitation method involves preparing a query with a stored value, changing the type of one of the fields, and then executing the query. The publication provides SQL code that causes an unpatched server to crash and leak memory addresses, but the final step with command execution is not disclosed.

Privilege nuance: crash and RCE have different thresholds

It is important to note a discrepancy between sources here. The researcher claims that a server crash can be triggered by a role with minimal privileges. At the same time, Red Hat in its assessment states that executing arbitrary code requires authentication and the ability to create or modify objects. None of the available sources clearly establishes whether the privileges of a default account are sufficient for full RCE. Thus, denial of service via a crash and remote code execution have different privilege requirements, and it would be incorrect to generalize the vulnerability as “RCE for any user.”

Historical depth

According to the researcher, the basic primitive — the ability to change a column’s type — appeared in a commit from 5 May 2004, and the exploitation technique via expanded-object pointers became possible after a change dated 14 May 2015. These dates are based on analysis of the commit history presented in the researcher’s technical write-up.

Other notable vulnerabilities in the release

Of the 52 fixed vulnerabilities, 32 received a CVSS score of 8.8 — the maximum score in this release. The following deserve particular attention:

  • CVE-2026-116322 — the only vulnerability that does not require authentication: an unauthenticated client can, through a specially crafted cancel request, trigger an emergency restart of a PostgreSQL 18 server. This is a separate issue from CVE-2026-6460 and should not be conflated with it.
  • CVE-2026-116314 (CVSS 8.8) — a vulnerability in the pg_restore client tool: a specially crafted archive can lead to arbitrary code execution as the user who ran the utility.

Details on all CVEs are available in the PostgreSQL vulnerability index and the official release announcement.

Patching specifics: update the server and extensions together

This release differs from typical PostgreSQL minor updates in that updating only the server does not provide full protection. The fix introduces a versioning mechanism for composite data types, and C extensions must be rebuilt with the new checks in mind.

According to a notice from the project’s RPM repository, extensions built for previous releases will continue to load, but “may not be protected against the vulnerabilities fixed in this release.” At the same time, extensions rebuilt for the new minor versions will not load on older servers due to missing new symbols. This creates a strict dependency: the server and all compiled extensions must be updated at the same time.

Update recommendations

  1. Update the server to the version corresponding to your major branch: 18.7, 17.12, 16.16, 15.20 or 14.25.
  2. Rebuild or update all C extensions at the same time as the server. Some extensions will require source code changes.
  3. If PostgreSQL is not running via the standard systemd unit (for example, under Patroni), perform a restart immediately after the update.
  4. Update client utilities (pg_dump, pg_restore, reindexdb, vacuumdb) on all machines where they are used.
  5. Reindex the affected indexes according to the release notes. If you use incremental backups, create a new full backup.
  6. Do not disable the new composite_type_mismatch parameter — the project warns that this carries security risks.
  7. PostgreSQL 14 has reached end of life: version 14.25 is the last release of this branch. Older major versions are also vulnerable, but no updates will be issued for them.

Despite the lack of confirmed exploitation in the wild, the presence of a public PoC exploit and the high CVSS score make this update a priority. It is especially critical for environments where untrusted users have authenticated access to the database with object-creation privileges — it is in such configurations that CVE-2026-6460 allows breaking out of the DBMS to the operating system level. Update the server and extensions at the same time, perform reindexing and create a new full backup.


CyberSecureFox Editorial Team

The CyberSecureFox Editorial Team covers cybersecurity news, vulnerabilities, malware campaigns, ransomware activity, AI security, cloud security, and vendor security advisories. Articles are prepared using official advisories, CVE/NVD data, CISA alerts, vendor publications, and public research reports. Content is reviewed before publication and updated when new information becomes available.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.