---
title: "PostgreSQL Fixes 52 CVEs, Including CVE-2026-6460 RCE"
url: https://erroneo.us/security/briefs/postgresql-november-2026-cve-2026-6460-rce/
description: "PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 fix 52 CVEs, including an 8.8 type confusion that lets object creators run OS code. Patch this week."
type: security-brief
section: "Security Digest"
date_published: 2026-11-12
date_modified: 2026-11-16
publisher: erroneo.us
author: erroneo.us Security Desk
verdict: "Patch this week"
cves: ["CVE-2026-6460", "CVE-2026-116322", "CVE-2026-116314", "CVE-2026-116330"]
severity: "high"
exploited: "public-poc"
kev: false
license: All rights reserved. Quote with attribution and a link.
---

# PostgreSQL Fixes 52 CVEs, Including CVE-2026-6460 RCE

**Verdict: Patch this week.** An attacker needs a database login first, and no attacks have been reported, but crash code is public, 32 of the fixes are rated 8.8, and any role that can create objects can reach code execution, so update every server and client this week.

- **Who must act:** Anyone self-hosting PostgreSQL where roles other than trusted administrators can log in and create objects, such as multi-tenant platforms, shared development databases and tools that let users run SQL, plus anyone who runs pg_restore on archives they did not create.
- **Who can relax:** Single-application databases reachable only by trusted roles can take the update in the normal weekly window, and managed-service users mainly need to confirm their provider has applied it.
- **Affected:** PostgreSQL 18 before 18.7; PostgreSQL 17 before 17.12; PostgreSQL 16 before 16.16; PostgreSQL 15 before 15.20; PostgreSQL 14 before 14.25; CVE-2026-116322: PostgreSQL 18 before 18.7 only
- **Fixed:** PostgreSQL 18.7; PostgreSQL 17.12; PostgreSQL 16.16; PostgreSQL 15.20; PostgreSQL 14.25 (final PostgreSQL 14 release)
- **CVEs:** CVE-2026-6460, CVE-2026-116322, CVE-2026-116314, CVE-2026-116330
- **CISA KEV:** no · **Exploitation:** Public proof-of-concept

## What to do

1. Find every server version with SELECT version(); and every client with pg_dump --version and pg_restore --version.
2. Update servers to 18.7, 17.12, 16.16, 15.20 or 14.25 and restart; packages may restart the service, but Patroni or custom units need a manual restart.
3. Update C-language extensions in the same change, because PostgreSQL says full protection requires rebuilding them.
4. Update client tools (pg_dump, pg_restore, psql, vacuumdb, reindexdb) on every host and CI image that runs them.
5. On managed services, check your provider's maintenance status and apply the pending minor version update.
6. Until patched, limit logins to trusted networks and roles, and do not run pg_restore on untrusted archives.
7. Plan the move off PostgreSQL 14, which is now end-of-life.

### How to check if you are affected

- Search server logs for backend crashes: grep -E 'terminated by signal (11|6)' in the PostgreSQL log directory, and investigate any you cannot explain.
- List roles that can create objects: SELECT r.rolname, n.nspname FROM pg_roles r, pg_namespace n WHERE has_schema_privilege(r.oid, n.oid, 'CREATE') AND NOT r.rolsuper; and note that TEMPORARY is granted to PUBLIC by default.
- On PostgreSQL 18, look for unexplained postmaster restarts, which CVE-2026-116322 can cause without a login.
- No indicators of compromise have been published as of Nov 16, 2026.

## What happened

On November 12, 2026, the PostgreSQL Global Development Group [released](https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/) PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25, fixing 52 security vulnerabilities and more than 140 other bugs. Thirty-two of the 52 are rated CVSS 8.8, and most of those let a logged-in user run arbitrary code as the operating system account that runs the database.

The headline issue is [CVE-2026-6460](https://www.postgresql.org/support/security/CVE-2026-6460/) (CVSS 3.1 8.8, `AV:N/AC:L/PR:L/UI:N`). The advisory says type confusion "allows an object creator to execute arbitrary code as the operating system user running the database, via ALTER ... SET DATA TYPE primarily," and that other DDL routes exist. The root cause is that stale values of a changed type could persist in data dictionary entries, PL/pgSQL variables and elsewhere. The [18.7 release notes](https://www.postgresql.org/docs/18/release-18-7.html) call the fix a "voluminous set of patches" and credit 17 reporters, among them Mehmet Ince, OpenAI's security research team, the Anthropic OSS program and Ada Logics.

Ince's [writeup](https://mehmetince.net/part-3-6-how-i-ended-up-turning-a-22-year-old-postgresql-type-confusion-primitive-into-rce-cve-2026-6460/) publishes SQL that crashes an unpatched backend and a step that leaks memory addresses. He describes, without publishing it in full, the route to code execution, and captions a video "Full working exploit on PostgreSQL 18.6."

Other fixes worth knowing:

- [CVE-2026-116322](https://www.postgresql.org/support/security/CVE-2026-116322/) (5.3) lets an unauthenticated network client trigger a server restart through cancel-request handling. Only PostgreSQL 18 before 18.7 is affected.
- CVE-2026-116314 (8.8): `pg_restore` can execute code from a crafted non-plain archive.
- CVE-2026-116330 (8.8): the `restore.sql` member of `pg_dump` tar output failed to block psql command injection.

PostgreSQL 14.25 is the final PostgreSQL 14 release.

## Who is affected

All supported major versions before the fixed minor releases. Exploiting CVE-2026-6460 requires a login role that can create objects. Red Hat's [assessment](https://access.redhat.com/security/cve/cve-2026-6460) describes the attacker as "an authenticated user with rights to create or alter database objects." Ince's proofs of concept create their types in the session's temporary schema. The PostgreSQL [privileges documentation](https://www.postgresql.org/docs/18/ddl-priv.html) confirms that `TEMPORARY` on databases is granted to `PUBLIC` by default, so do not assume a role is harmless because it lacks `CREATE` on `public`.

Managed services are affected too. Ince says he shared proofs of concept with AWS (RDS and Aurora), Azure, Google AlloyDB, Supabase, Databricks, Ubicloud and ClickHouse from mid-August, and that some applied their own mitigations before the upstream release. Each provider's patch status is not disclosed as of November 16, 2026.

## Do you really need to act?

Yes, on a weekly rather than emergency schedule for most teams. The [CVE record](https://www.cve.org/CVERecord?id=CVE-2026-6460) carries CISA's assessment of "Exploitation: none" and "Automatable: no", and nothing here gives an anonymous attacker code execution. The worst unauthenticated issue is a PostgreSQL 18 restart.

The risk is concentrated where untrusted people get SQL access: multi-tenant platforms, internal analytics or BI tools that hand out roles, shared development databases and hosted notebooks. In those settings, one ordinary account becomes a shell on the database host. SQL injection in an application whose role owns its own tables is a second path. Restoring a dump from an untrusted source is a third, separate client-side risk.

The update needs care. The release notes say full protection "requires rebuilding C-language extensions," and some extensions need source changes. The [PGDG yum repository](https://yum.postgresql.org/news/extensions-require-minor-release/) now makes extensions require the new minor release, so a version-locked server blocks extension updates. A new `composite_type_mismatch` setting can disable the new checks, but the project warns this "carries security risks."

## What to do now

1. Inventory versions: `psql -c 'SELECT version();'` on each server, and `pg_dump --version` and `pg_restore --version` on hosts and CI images.
2. Update to 18.7, 17.12, 16.16, 15.20 or 14.25. The server package restarts a running service, but as [Devrim Gündüz notes](https://people.planetpostgresql.org/devrim/index.php?/archives/138-PostgreSQL-November-2026-minor-releases-update-the-server-and-extensions-together.html), you must restart PostgreSQL yourself under Patroni or a custom unit. For containers, pull and redeploy the new `postgres` image tags.
3. Update C-language extensions in the same change. On RHEL-family systems, `sudo dnf update` updates both together, and you should remove any `dnf versionlock` pins first.
4. Update client tools everywhere they run, including backup hosts.
5. Follow the post-update steps in the announcement: reindex affected GIN, `gist_trgm_ops` and `bpchar` B-tree indexes, and take a new full backup if you use incremental backups.
6. Until patched, restrict network access to trusted hosts and review which roles can create objects. Red Hat suggests `REVOKE CREATE ON SCHEMA public FROM PUBLIC;`, but that does not cover temporary objects.

## How to tell if you were hit

No indicators of compromise have been published. The public crash code kills a backend, so search logs for `terminated by signal 11` or `signal 6` and match crashes to sessions and roles. On a host where a non-administrative role could log in, review files and processes owned by the `postgres` OS user for anything unexpected. On PostgreSQL 18, unexplained full restarts before the update may point to CVE-2026-116322.

## Timeline

- Mid-August 2026 — Ince shares proofs of concept with AWS and Azure and details with Supabase, according to his writeup.
- Nov 9, 2026 — Date of Ince's writeup, which says the security commits landed that day.
- Nov 12, 2026 — PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 released with 52 CVEs fixed. The CVE records are published, and the PGDG yum repository ties extensions to the new minor releases.
- Nov 13, 2026 — [The Hacker News](https://thehackernews.com/2026/11/postgresql-patches-52-flaws-including.html) reports the release. No exploitation is known.
- Nov 16, 2026 — Devrim Gündüz advises updating the server and extensions together.

## Sources

1. [PostgreSQL — PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25 and 19 RC 2 released](https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/)
2. [PostgreSQL — CVE-2026-6460 security advisory](https://www.postgresql.org/support/security/CVE-2026-6460/)
3. [PostgreSQL — CVE-2026-116322 security advisory](https://www.postgresql.org/support/security/CVE-2026-116322/)
4. [PostgreSQL — Release 18.7 notes](https://www.postgresql.org/docs/18/release-18-7.html)
5. [CVE.org — CVE-2026-6460](https://www.cve.org/CVERecord?id=CVE-2026-6460)
6. [PostgreSQL — Documentation: Privileges](https://www.postgresql.org/docs/18/ddl-priv.html)
7. [PostgreSQL Yum Repository — Extensions now require the latest minor release](https://yum.postgresql.org/news/extensions-require-minor-release/)
8. [Devrim Gündüz — PostgreSQL November 2026 minor releases: update the server and extensions together](https://people.planetpostgresql.org/devrim/index.php?/archives/138-PostgreSQL-November-2026-minor-releases-update-the-server-and-extensions-together.html)
9. [Mehmet Ince — How I ended up turning a 22-year-old PostgreSQL type confusion primitive into RCE (CVE-2026-6460)](https://mehmetince.net/part-3-6-how-i-ended-up-turning-a-22-year-old-postgresql-type-confusion-primitive-into-rce-cve-2026-6460/)
10. [Red Hat — CVE-2026-6460](https://access.redhat.com/security/cve/cve-2026-6460)
11. [The Hacker News — PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE](https://thehackernews.com/2026/11/postgresql-patches-52-flaws-including.html)

---
Source page: https://erroneo.us/security/briefs/postgresql-november-2026-cve-2026-6460-rce/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt
