PEHAMLIMITED
All updates
Update

PostgreSQL CVE-2026-6460: Exploit Code Is Public. Patch, and Rebuild Your Extensions

PostgreSQL's November release fixes 52 vulnerabilities. The worst, CVE-2026-6460 (CVSS 8.8), lets a logged-in user who can create a table run code on the database server, and proof-of-concept code is already public. Here is who is exposed and how to patch properly, including the extension rebuild most guides skip.

14 Nov 2026Team Peham#Security#DevOps
Postgres November CVE

On 12 November the PostgreSQL project shipped one of the largest security releases in its history: 52 vulnerabilities fixed across every supported branch. The one to act on first is CVE-2026-6460, rated 8.8. It lets a logged-in database user who is allowed to create objects run code as the operating system account behind the database. Proof-of-concept code appeared on GitHub a day later.

The short answer: upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20 or 14.25, and update or rebuild your C-language extensions in the same step. This is not an unauthenticated attack. The attacker needs a database login that can create objects, but on older clusters that can be every login role you have.

What the bug is

CVE-2026-6460 is a type confusion flaw (CWE-843) in the core server. PostgreSQL did not track typed values closely enough, so after certain schema changes an old value could still be held somewhere in the server and then be read as if it had the new type. The main trigger is , though the advisory lists other DDL routes, such as adding a column, rolling back, and adding it again. Reporting on the release describes the flaw as roughly 22 years old.

Who is exposed

  • Every version below the fixed releases. That covers all of 14.x to 18.x before this update. PostgreSQL 13 and older are unsupported and get no fix.
  • Any non-superuser role that can create objects. That includes roles with CREATE on any schema, database owners, and roles with TEMPORARY rights, which PUBLIC receives by default on new databases.
  • Clusters first created on PostgreSQL 14 or older. On these, every login role can create objects in the public schema, and that default survives pg_upgrade and dump and restore.
  • Applications with a SQL injection bug. If your app's database role can create tables, an injection flaw that used to mean data theft could now mean code running on the database host. Shared and multi-tenant databases carry the same risk.

Is it being exploited?

No confirmed attacks have been reported, and the CVE was not on CISA's Known Exploited Vulnerabilities list when we checked on 14 November. What has changed is that public proof-of-concept code now exists. We have seen how short that window can be: PHP2Shell went from patch to public exploit in four days.

How to fix it

  1. Check your version. Run on each cluster. You need at least 180007, 170012, 160016, 150020 or 140025.
  2. Upgrade the server and extensions together. The fix changes how the server checks composite values, and the release notes say full protection requires rebuilding C-language extensions. Upgrade packaged extensions such as pgvector alongside the server, and rebuild anything you compiled yourself. Some extensions may need source changes.
  3. Restart and verify. The package upgrade restarts the server, so patch replicas first, switch over, then patch the old primary. A patched server recognises the new setting. Leave it at its default; the project warns that turning the checks off carries security risk.
  4. Redeploy containers and check managed services. Pull a patched image tag and recreate the container; a running container keeps its old binary. If you use a managed database, check your provider's status page for when the fixed minor version lands.
  5. Plan your exit from PostgreSQL 14. 14.25 is the final release of that branch. It is now end of life and will get no further security fixes.

Can't patch today? Reduce the risk

None of these is a fix, but they narrow the path while you schedule the upgrade:

  • Remove public create rights. Run in each database and in template1. Test on staging first, because apps that create tables at runtime will break. This does not remove TEMP rights.
  • Audit who can create objects. List login roles with CREATE or TEMP rights and remove what your applications do not need.
  • Close the port. Port 5432 should only be reachable from the hosts that need it, never the open internet.

A note on distro packages: as of 14 November the official PGDG apt and yum repositories carried fixed builds for 14 to 18 and Debian 13 was patched, but Ubuntu 24.04's own archive was still serving 16.15 and Red Hat was offering mitigations only for RHEL. This is changing daily, so check your distribution's security tracker rather than assuming an update has arrived.

Need help?

PostgreSQL sits behind much of the software we build and host at Peham. Our Cloud & DevOps team can find every vulnerable cluster across your servers and containers, upgrade the server and its extensions together, and verify the fix.

Book a free 30-minute database security check and talk it through with our engineers.

Sources