The PostgreSQL project shipped one of its largest security releases in years on November 12, 2026. Versions 18.7, 17.12, 16.16, 15.20 and 14.25 fix 52 security flaws. According to The Hacker News, the project rates 32 of them at CVSS 8.8, the highest score in the release. The headline bug, CVE-2026-6460, is a type-confusion flaw that lets a database user who can create objects run arbitrary code on the server as the operating-system account PostgreSQL runs under. Researcher Mehmet Ince traces its roots to a change made in 2004.
There are no reports of anyone exploiting it. The Hacker News reports that the PostgreSQL project has not reported any attacks and that CISA's assessment in the CVE record lists exploitation as "none". Even so, a public technical writeup by Ince now exists, and there is no workaround for servers that cannot be updated. That makes this a patch-now release, not one to leave for the next maintenance window.
What exactly is broken?
PostgreSQL's advisory describes CVE-2026-6460 as a type confusion after an ALTER ... SET DATA TYPE operation. That is the DDL (data definition language) statement used to change a column's data type, for example from integer to text.
"Type confusion" means one part of a program treats a piece of memory as one kind of data while it actually holds another. The advisory says the system had inadequate tracking of typed values, so stale values could appear in data dictionary entries, PL/pgSQL variables and other parts of the system. It says an object creator can use this to execute arbitrary code as the OS user running the database. It also notes that ALTER ... SET DATA TYPE is the primary route but not the only one: other DDL attack routes exist.
The Hacker News explains that the flaw involves composite types, which are built from named fields that each have their own data type. A field's type can be changed while older values of that type are still held elsewhere in the server, which can then read an old value as if it had the new type. The project's fix adds version checks so the server can detect a value that no longer matches its type.
According to The Hacker News, Ince traces the root of the flaw to May 5, 2004, when PostgreSQL gained the ability to change a column's type, which is where the "22-year-old" label comes from. His code-execution technique relies on a later change made on May 14, 2015.
The advisory lists a CVSS 3.0 score of 8.8 with the vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. That means the attack works over the network, is low complexity, needs only low privileges and no user interaction, and has high impact on confidentiality, integrity and availability. The affected component is the core server. NVD has published the record, which carries a CVSS 3.1 vector with the same metrics and the same 8.8 score, but still lists it as "Awaiting Analysis".
Who can actually exploit this?
The phrase "privileges required: low" matters here. This is not an unauthenticated internet-wide bug. The project's advisory describes the attacker only as someone who can create objects, without saying which privileges that takes. Red Hat, according to The Hacker News, says an attacker needs a database login with the ability to create or modify objects. Ince wrote that he could trigger the crash as a lowest-privileged login role, but none of the sources says whether an account with only default privileges can go beyond the crash to run code.
That still leaves plenty of environments worth a look. Wherever accounts hold CREATE rights, whether multi-tenant or hosted databases, application accounts granted broad DDL rights for migrations, or developer and reporting users on shared clusters, an attacker who obtains such a login could gain code execution as the PostgreSQL service account. Code running under that account would have the rights of the OS user that runs PostgreSQL. These examples are illustrative; the sources do not name specific affected deployment types.
Managed cloud providers were brought in early. According to The Hacker News, Ince adapted the exploit for managed PostgreSQL services and privately shared proofs of concept with their security teams in August. The providers he worked with include AWS (Aurora and RDS), Microsoft (Azure PostgreSQL), Google (AlloyDB), Supabase, Databricks and Ubicloud. The writeup does not give each service's current patch status, so customers should check their provider's status pages to confirm their instances have moved to fixed builds, rather than assuming they have.
The one bug that needs no login
Based on the scores in the project's vulnerability index, The Hacker News reports that only one server flaw requires neither a login nor any user action: CVE-2026-116322. It lets an unauthenticated client trigger a restart of PostgreSQL 18 servers. That is a denial-of-service issue, not code execution. But for any PostgreSQL 18 instance reachable from untrusted networks, it means someone who has never logged in can force restarts. It is another strong reason to patch, and another reminder that database ports should not be exposed to the internet.
Not just the server: clients and extensions too
This release reaches past the server binary. The Hacker News reports that a crafted archive can make pg_restore run code as the user running it, and that a compromised source server can make psql run code through the restore script in pg_dump's tar output. That matters for anyone who restores dumps from sources they don't fully trust, or who connects administrative clients to servers they don't control. Update client packages on workstations, jump hosts and backup servers as well as on the database hosts.
Administrators also need to rebuild or update C-language extensions alongside the server. Per The Hacker News, extensions built against older releases still load, but, according to a notice from the project's RPM package maintainers, they "may not be protected from the vulnerabilities fixed in this release". Some extensions will also need source-code changes, and extensions rebuilt for the new releases can fail to load on older servers. That covers third-party extensions and any in-house ones you have written.
The update also introduces a new setting, composite_type_mismatch. The guidance reported by The Hacker News is direct: do not use it to turn off the new checks, because the project says doing so carries security risks. Treat it as part of the fix, not as a compatibility switch.
End of the line for PostgreSQL 14
PostgreSQL 14.25 is the last release of the 14 branch, which is now end-of-life. Installations on 14 should apply 14.25 straight away to close these holes, then plan a major-version upgrade. No further security fixes will come for that line. The Hacker News adds that older major versions are also affected and received no update.
What It Means for Defenders
Who is affected: Every PostgreSQL release older than 18.7, 17.12, 16.16, 15.20 or 14.25, per the PostgreSQL advisory and the NVD record. Self-managed servers and any products that bundle PostgreSQL should be checked against those versions.
What to patch:
- Upgrade to 18.7, 17.12, 16.16, 15.20 or 14.25, matching your major version.
- Rebuild or update every C-language extension at the same time as the server. If PostgreSQL runs outside its package's own service unit, for example under Patroni, restart it right after updating.
- Update client tools (
psql,pg_restore,pg_dump) on admin workstations, CI runners and backup hosts. - After updating, follow the reindexing steps in the release announcement. If you use incremental backups, take a new full backup and base later incremental backups on it.
- Do not use
composite_type_mismatchto disable the new checks. - On PostgreSQL 14, apply 14.25 now and schedule a move to a supported major version.
- On managed services, confirm with your provider that your instances are on patched builds.
What to check while you wait: There is no workaround for CVE-2026-6460, so these steps reduce exposure but are not a substitute for patching. Audit which roles hold CREATE privileges on databases and schemas, and take them away from application and reporting accounts that don't need DDL. Make sure no PostgreSQL listener is reachable from the internet. That matters most on version 18, given the unauthenticated restart bug. Review logs for unexpected DDL activity and unexplained server restarts.
What to rotate: No exploitation has been reported. If you find signs of unexpected restarts or unexplained DDL from low-privilege accounts on a server that was exposed before patching, consider treating the host as possibly compromised. Rotate database credentials and any secrets readable by the PostgreSQL OS account.
For CMMC and federal contractors: A high-severity, network-reachable flaw with no workaround on a system that stores CUI is a strong candidate for prompt remediation under your flaw-remediation practice. Record the patch date and version for each instance, and track your PostgreSQL 14 migration as a documented remediation item.