PostgreSQL Vulnerability CVE-2026-6460: Object Creators Can Run Code on the Database Server, 52 Flaws Fixed, and Why Updating Without Rebuilding Extensions Is Not Enough
PostgreSQL fixed 52 security flaws, including CVE-2026-6460, which lets an account that can create objects run code on the server. Here are the fixed versions, the extension rebuild step and the PostgreSQL 14 end of life.
Where Worldwide
On this page 9 sections
The PostgreSQL project has released updates that fix 52 security vulnerabilities. One of them, CVE-2026-6460, lets a database account that is allowed to create objects run its own code on the server as the operating system user that runs the database. If your websites, apps or business systems use PostgreSQL (often shortened to Postgres), install the fixed version for your branch this week. Then check your extensions, because the project says the update alone does not give full protection.
The release announcement is dated Thursday, November 12, 2026. It is also the final release of PostgreSQL 14, which is now end-of-life.
What is CVE-2026-6460?
CVE-2026-6460 is a type confusion flaw in PostgreSQL. The project's own advisory is titled "PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code" and lists a severity score of 8.8.
In plain terms, the advisory says an object creator can execute arbitrary code as the operating system user running the database. The main route is the ALTER ... SET DATA TYPE command, which changes the data type of something that already exists in the database. The advisory says the cause is that PostgreSQL did not track certain typed values closely enough: values that do not identify their own type.
The phrase to notice is object creator. The advisory describes the attacker as someone with a database account that can create objects, not an outsider with no login. But the damage goes beyond the database. Someone who uses the flaw is running code on the server itself, with the same operating system rights as the database service.
What is confirmed and what is not
Confirmed by PostgreSQL's advisory, release notes and release announcement:
- CVE-2026-6460 lets an object creator run arbitrary code as the operating system user running the database.
- PostgreSQL versions before 18.7, 17.12, 16.16, 15.20 and 14.25 are affected.
- The advisory lists a severity score of 8.8.
- The release fixes 52 security vulnerabilities and over 140 bugs reported over the last several months.
- Full protection requires rebuilding C-language extensions, and some extensions need source-code changes.
- PostgreSQL 14 is now end-of-life and will no longer receive security and bug fixes.
Not known from the sources we checked:
- Whether CVE-2026-6460 has been used in real attacks. The sources do not say either way.
- The details of the other security fixes in this release. This post covers CVE-2026-6460.
- Any workaround short of updating. The sources we checked list none.
PostgreSQL fixed versions
| If you run | Update to | Note |
|---|---|---|
| Before PostgreSQL 18.7 | 18.7 | Check C-language extensions after updating |
| Before PostgreSQL 17.12 | 17.12 | Check C-language extensions after updating |
| Before PostgreSQL 16.16 | 16.16 | Check C-language extensions after updating |
| Before PostgreSQL 15.20 | 15.20 | Check C-language extensions after updating |
| PostgreSQL 14 | 14.25 | Final release of 14, plan a move to a supported branch |
| Older than 14 | No fixed version named | The sources list fixed versions for 14.25, 15.20, 16.16, 17.12 and 18.7 only |
Do I need to rebuild PostgreSQL extensions?
If any of your extensions are written in C, probably yes. The PostgreSQL 18.7 release notes say the fix adds defenses against problems that happen when a composite type is altered while other operations are working on data of that type. The same notes add the line that is easy to miss: "For full protection, this change requires rebuilding C-language extensions, and there are some extensions that will require source-code changes."
So installing the new PostgreSQL version is step one, not the finish line. Every C-language extension your databases load needs to be rebuilt against the updated version, and some will need their developers to change the code first. If an extension came from a vendor or a package source, ask the supplier whether a rebuilt or updated build is ready. That instruction comes from the 18.7 notes. If you run an older branch, look for the same step in that branch's own release notes, and do not assume it is missing.
We have covered this gap before with a different product: updated is not the same as patched. A server can show the new version number while still running pieces that were built for the old one.
PostgreSQL 14 end of life
The announcement says this is the final release of PostgreSQL 14 and that 14 will no longer receive security and bug fixes. Updating to 14.25 closes CVE-2026-6460 now, but the next PostgreSQL flaw will not be fixed on 14. If you are on 14, update to 14.25 this week and schedule an upgrade to a supported branch.
What to do this week
- List every PostgreSQL database you run. Include production, staging and test copies, databases bundled inside apps or appliances, and any that your hosting provider runs for you.
- Check the exact version on each one and compare it with the table above.
- Update to 18.7, 17.12, 16.16, 15.20 or 14.25, depending on the branch.
- List the C-language extensions each database loads, rebuild them against the new version, and ask suppliers whether any need source-code changes.
- For hosted databases, ask the provider when they will apply the fix and whether they also handle extension rebuilds.
- Review which accounts can create objects. Take that right away from logins that do not need it, such as reporting users or old contractor accounts. This is good housekeeping, not a replacement for the update.
- If you are on PostgreSQL 14, schedule the move to a supported branch.
- Write down what you changed and when, so the next update starts from a known list.
Why it matters for a business network or website
The database is where the valuable data usually sits: customer records, orders, invoices and login details. A flaw that lets a database account run code on the server turns a database problem into a server problem.
Ask one direct question: can your application's own database login create objects? If it can, anyone who gets hold of that login, through a leaked password or a flaw in the app, would count as an object creator in the advisory's sense. That is why needing an account does not mean the risk is low. Accounts get shared, reused and forgotten. Once someone is running code on the database server, they can start looking for a way into the rest of your network.
There is also the question of who owns the job. If nobody is clearly responsible for updating the database behind your website or app, this release is a good moment to settle that. Read who is patching the software that runs your business for how to set that up. If you host your own servers, our self-hosting and infrastructure page covers running and maintaining them.
PostgreSQL CVE-2026-6460 questions people are asking
Is CVE-2026-6460 being exploited?
The sources we checked do not say whether it has been used in attacks. Treat that as unknown, not as safe, and update anyway.
Can someone with no database login use this flaw?
The advisory describes the attacker as an object creator, meaning an account that can create objects in the database. It does not describe an attack by someone with no account.
Which PostgreSQL version fixes CVE-2026-6460?
18.7, 17.12, 16.16, 15.20 and 14.25. Any version before those is affected.
Is updating PostgreSQL enough?
Not on its own. The 18.7 release notes say full protection requires rebuilding C-language extensions, and some extensions need source-code changes.
How serious is CVE-2026-6460?
The PostgreSQL advisory lists a severity score of 8.8. An attacker who uses it can run code on the server as the operating system user that runs the database.
How many vulnerabilities did this PostgreSQL update fix?
52 security vulnerabilities and over 140 bugs, according to the release announcement.
Is PostgreSQL 14 still supported?
No. 14.25 is its final release, and 14 will no longer receive security and bug fixes.
The bigger lesson
A version number tells you what is installed. Whether the system is actually protected is something you have to check. This PostgreSQL release shows why: the update fixes the database, but full protection also depends on the extensions loaded into it and on knowing which accounts can reach the flaw. Keep a list of what you run, who updates it and what plugs into it, and an update like this takes an afternoon instead of a scramble.
See how we approach security hardening, or get a quote to have your servers checked.
Get security alerts like this by email, with our free checklist, at /security-alerts.
Sources: PostgreSQL security advisory for CVE-2026-6460; PostgreSQL 18.7 release notes; PostgreSQL release announcement.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Microsoft 365 Outage Phishing: Fake Held-Mail Emails Used the November 12 Disruption as Bait, What Is Confirmed and How to Check Who Clicked
Phishing emails used the November 12 Microsoft 365 outage as cover, falsely claiming messages held during the...
Fireworks AI Data Breach: Uber Notifies 149,346 People After Hackers Stole Driver License Data From Its AI Vendor, What Is Confirmed and What Businesses Should Check
Uber says hackers stole drivers' names, addresses, dates of birth and license numbers in a breach at vendor Fi...
PostgreSQL Security Update: 52 Vulnerabilities Fixed Including CVE-2026-6460, PostgreSQL 14 Reaches End of Life, and the Versions to Install
PostgreSQL's November 12 update fixes 52 security vulnerabilities, including CVE-2026-6460, a code execution f...