The PostgreSQL project has released updates that address 52 security flaws. The most serious of these is a type confusion vulnerability, tracked as CVE-2026-6460 and assigned a CVSS score of 8.8, that allows a database user with the ability to create objects to run code on the database server.

What the flaw allows

Code executed through this flaw runs with the privileges of the PostgreSQL server process. An attacker who already holds valid database credentials and the right to create objects could therefore escalate from a limited database role to code execution on the underlying host. The attack requires authentication, which narrows the exposure, but it still matters in environments where many accounts can create objects or where credentials have been obtained through other means.

Patching requirements

  • Apply the updates released in the latest PostgreSQL maintenance release, which cover this flaw and 51 others.
  • Rebuild any C-language extensions installed on the server. The source indicates that updating the core server alone does not provide full protection from this issue.
  • Review which accounts hold object-creation privileges and restrict them to the minimum required.

Why it matters

The vulnerability is notable because it reportedly dates back about 22 years, meaning it has existed across a long span of released versions. Administrators should not assume that older, stable deployments are free of the issue. Because extensions are a common part of PostgreSQL installations, the requirement to rebuild them is an easy step to overlook, and teams that skip it may remain exposed after applying the core update.

Security teams should prioritize inventorying PostgreSQL instances, confirming the patch level of each, and verifying that custom or third-party C extensions have been recompiled against the fixed version.