PostgreSQL released updates on 12 November fixing 52 security flaws. The most serious, CVE-2026-6460 (CVSS 8.8), lets a user with permission to create objects run code on the server. It affects every version before 18.7, 17.12, 16.16, 15.20 and 14.25. If you use it, update as soon as possible and recompile your C extensions.
The essentials
- The PostgreSQL project released versions 18.7, 17.12, 16.16, 15.20 and 14.25 on 12 November, with 52 security fixes, according to The Hacker News.
- CVE-2026-6460 (CVSS 8.8) is a type confusion involving composite types, a bug that had been in the code for 22 years. A user allowed to create objects can run code with the rights of the operating system user running PostgreSQL.
- 32 of the 52 flaws score 8.8, the highest in the batch. CVE-2026-116322 is the only one that needs no login or user action: it lets an unauthenticated client restart PostgreSQL 18 servers.
- There are no known attacks, and CISA's assessment in the CVE record lists exploitation as "none". Even so, researcher Mehmet Ince has published an analysis with a partial exploit.
- PostgreSQL 14 reaches end of life: 14.25 is its final release.
Am I affected if my database runs on AWS, Azure or Google?
Many ERPs, CRMs, web apps and SaaS products run on PostgreSQL, even if you never see it. If it runs on your own servers or in containers, patching is your job.
If it runs on a managed service, the honest answer is that you don't know. Ince adapted the exploit to these services and privately shared proofs of concept in August with AWS (Aurora and RDS), Microsoft (Azure PostgreSQL), Google (AlloyDB), Supabase, Databricks and Ubicloud. His analysis doesn't state the patch status of each service. You need to ask your provider.
Is it urgent if nobody is exploiting it?
Yes. Ince has published the SQL that crashes an unpatched server and a second step that leaks memory addresses. The final step that runs a command is missing, but the path is mapped out. He says he can trigger the crash with a minimally privileged login role. The sources don't say whether an account with default privileges can go on to execute code.
There is no mitigation for servers that can't be updated yet. The project warns against disabling the new checks with the composite_type_mismatch setting.
The batch also fixes client tools. A crafted file can make pg_restore run code. A compromised source server can make psql run code through pg_dump's tar output. That affects the machines of whoever runs backups and restores, not just the server.
What if I'm still on PostgreSQL 14 or older?
14.25 is the last release in that branch. Older major versions are also affected and won't get an update. Installing 14.25 covers you today, but the next flaw won't be patched.
What to do today
- Inventory every PostgreSQL instance: production, testing, containers and managed services. Check the version with
SELECT version();. - Compare it with 18.7, 17.12, 16.16, 15.20 and 14.25. Check these numbers against the official release notes before acting.
- Schedule the minor update, starting with instances exposed to the internet or shared with third parties. Internet-facing PostgreSQL 18 goes first.
- Recompile the C extensions installed on the server. Some will need source code changes. If you install from RPM packages, follow the repository notes.
- Review which accounts can create objects. Cut the list to the minimum and remove that privilege from application users.
- If you use a managed service, open a ticket and ask in writing for the patch status of CVE-2026-6460.
- Don't restore untrusted dumps with
pg_restoreuntil your client tools are updated. - If you're still on PostgreSQL 14 or older, set a date for migrating to a supported version.
What it means for a small business
The flaw requires an account allowed to create objects. That sounds like a barrier, but in many companies it isn't. Applications often connect with a user that can do everything, because that's how it was installed and it worked. If an attacker gets into that application, they inherit that permission and, with this flaw, jump to the server's operating system.
Our view: update this week, not in the next quarterly window. With a partial exploit public, the missing step will likely appear soon. And use the opportunity to review privileges, which will also protect you from the next flaw.
On managed services: outsourcing the database doesn't mean outsourcing the question. If your provider won't tell you when they patched, don't assume they have.
One honest caveat: this story relies on a single secondary source. The versions and scope are consistent, but check the project's official advisory before touching production. If you need help inventorying instances or reviewing permissions, our cybersecurity team handles this kind of review.
Frequently asked questions
Is there a mitigation if I can't update yet?
There's no official mitigation. What you can do is reduce the number of accounts allowed to create objects. Don't disable the checks with composite_type_mismatch.
Is installing the minor version enough?
No. Full protection requires recompiling the server's C extensions, and some will need changes to their source code.
Is it being exploited already?
There are no known attacks and CISA lists exploitation as "none". But a public analysis with a partial exploit exists.