Vulnerability alert · 14 Nov 2026
If you run self-managed PostgreSQL, you are affected unless you are already on 18.7, 17.12, 16.16, 15.20 or 14.25, released on 12 November 2026. The most serious flaws let a logged-in database user who can create or alter objects run code on the server as the operating system account running PostgreSQL. Patch first where untrusted or semi-trusted users have database logins with CREATE rights, and PostgreSQL 18 instances reachable from untrusted networks. Managed services (RDS, Azure Database for PostgreSQL, AlloyDB and similar) are patched by the provider on its maintenance schedule.
The PostgreSQL security page lists the fixes. Most of the high-severity ones share a pattern: type confusion, use-after-free or buffer overflow in the core server, reachable by an authenticated user (CVSS 3.x vector AV:N/AC:L/PR:L/UI:N, score 8.8). The affected areas include:
ALTER … SET DATA TYPE (CVE-2026-6460), PL/pgSQL record fields, parallel query, the min/max aggregates, foreign data wrapper batch inserts.ts_rank_cd() and tsvector_delete().restore.sql fails to block psql command injection (CVE-2026-116330); pg_dump on 18 allows SQL injection through a not-null constraint name (CVE-2026-116318).The fixed versions are the same for all of them: 18.7, 17.12, 16.16, 15.20 and 14.25.
CVE-2026-6460 is a type-confusion flaw. When a column's type changes, values of the old type can still exist in the server and be read as the new type. A user who can create objects can turn that into code execution as the OS user running PostgreSQL. Researcher Mehmet Ince traced the root to a 2004 change that added column type changes. He published a working exploit demonstrated on 18.6 that stops short of the final command-execution step (The Hacker News).
The fix adds checks that detect values that no longer match their type. That is why C-language extensions need to be rebuilt against the fixed server for full protection. Patched builds have a new composite_type_mismatch setting, which the project advises leaving at its default.
Exploitation status: none reported, and CVE-2026-6460 is not in CISA's KEV catalog. With a public exploit chain most of the way there, that can change, so don't wait for it.
Only a few of the 52 need no login. The one to know is CVE-2026-116322: a pre-authentication cancel request can leak a spinlock (CVSS 5.3, availability impact only). The Hacker News reports that an unauthenticated client can use it to make a PostgreSQL 18 server restart. It's a denial of service, not code execution, but anyone who can reach the port can trigger it. A PostgreSQL port reachable from the internet is worth closing regardless.
Check the running version of every cluster, not the installed package; a server that wasn't restarted still runs the old binary. On a patched server, this query returns error in the second column; an empty value means unpatched (ComputingForGeeks):
SELECT current_setting('server_version'),
current_setting('composite_type_mismatch', true);
Then check who can create objects, since that is the precondition for CVE-2026-6460. Clusters first created on PostgreSQL 14 or older let every login create in the public schema, and that default survives dump/restore and pg_upgrade. Run this in each database:
SELECT r.rolname, n.nspname
FROM pg_roles r CROSS JOIN pg_namespace n
WHERE r.rolcanlogin AND NOT r.rolsuper
AND n.nspname NOT LIKE 'pg\_%' AND n.nspname <> 'information_schema'
AND has_schema_privilege(r.oid, n.oid, 'CREATE');
Any application login in the result is a role that could exploit the bug if its credentials leak, or through SQL injection in the application.
pg_hba.conf and firewall rules.gist_trgm_ops, and B-tree indexes on bpchar columns declared without a length. Run REINDEX TABLE on tables that throw "missing chunk number" errors (Help Net Security).There is no workaround that removes the bugs. You can shrink who can reach them:
REVOKE CREATE ON SCHEMA public FROM PUBLIC; in every database, including template1, on clusters created on 14 or older. Test on staging first: applications that create tables at runtime will break.log_statement = 'ddl') and alert on unexpected ALTER TABLE from application roles.Our stack check alerts you when a product you run lands in CISA's exploited list, and the radar tracks which new CVEs are climbing in exploitation likelihood before that happens.
PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25, released on 12 November 2026. Versions 13 and older are out of support and received no fix.
No. It needs a database login that can create or alter objects. In practice that includes application roles with CREATE rights and any login on clusters first created on PostgreSQL 14 or older, where the public schema is writable by default.
No attacks have been reported and it is not in CISA's Known Exploited Vulnerabilities catalog as of 14 November 2026. A researcher has published most of an exploit chain, so treat it as a priority patch anyway.
We inventory PostgreSQL instances and their exposure, tighten roles and network access, and fold database patching into your vulnerability process so NIS2 and PCI DSS evidence is ready when the auditor asks.
Request a quote →