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 flaw rated 8.8. PostgreSQL 14 gets its final release. Here are the versions to install and how to check.
Where Worldwide
On this page 9 sections
If any of your websites, apps or internal systems keep their data in PostgreSQL, you have a security update to install. The PostgreSQL Global Development Group released new versions on Thursday, November 12, 2026. They fix 52 security vulnerabilities, including CVE-2026-6460, a flaw the project says can execute arbitrary code. If you still run PostgreSQL 14 you have a second problem: this is its final release, and it will get no more security fixes.
This post covers what is confirmed, what is not known, which version to install and how to check this week.
What the PostgreSQL November 2026 security update fixes
The update was posted on 2026-11-12 and covers all supported versions: PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25. It also includes the second release candidate of PostgreSQL 19. The release announcement says it fixes 52 security vulnerabilities and over 140 bugs reported over the last several months.
This is a minor update, not a major upgrade. The announcement says: "As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply stop PostgreSQL and update its binaries."
So most of the work is planning a short maintenance window. You are not migrating data.
CVE-2026-6460: what is confirmed
PostgreSQL's own security page lists the flaw as "CVE-2026-6460: PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code" and gives it a severity score of 8.8. It also states: "PostgreSQL Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected."
In plain English: ALTER ... SET DATA TYPE is the kind of command used to change what type of data a column holds. Type confusion means the software ends up treating data as the wrong type. The advisory's title says this mistake, after such a command, can lead to arbitrary code being executed. Arbitrary code means code chosen by whoever triggers the flaw, not code PostgreSQL meant to run.
What is not known
- Exploitation. Neither the advisory nor the release announcement says whether anyone is exploiting CVE-2026-6460 or the other flaws.
- Who can trigger it. We could not confirm what access an attacker needs. Do not assume it requires a login, and do not assume it does not.
- The rest of the list. We confirmed details for three of the 52 fixes. For the others, read the release announcement itself.
The pg_dump and pg_restore flaws: your backups are in scope
Two of the fixes are in the backup tools many teams rely on. The announcement lists:
- "pg_dump not-null constraint name allows SQL injection"
- "pg_restore executes arbitrary code due to missing non-plain archive validation"
These tools often run somewhere other than the database server: a backup server, a scheduled job on an app server or a developer's laptop. If you update the server and forget those machines, part of the problem stays in place. Until they are updated, be careful about restoring any archive you did not create yourself.
PostgreSQL 14 end of life: what it means
The release announcement is direct: "This is the final release of PostgreSQL 14. PostgreSQL 14 is now end-of-life and will no longer receive security and bug fixes."
That makes 14.25 the last patch version 14 will get. Install it now because it closes the flaws above, but treat it as a stopgap: any flaw found in PostgreSQL 14 from now on stays open. Moving to a newer major version is a bigger job than a minor update, so plan it. Test on a copy of the database, check that your applications work with the new version, then schedule the cutover. If you run your own servers, our self-hosting and infrastructure page explains how we approach that kind of work.
If you run a version older than 14, it is not on the list of supported versions that received this update.
Which PostgreSQL version should I install?
| If you run | Install this version or later | Notes |
|---|---|---|
| PostgreSQL 18.7 | 18.7 | Minor update: stop PostgreSQL, update binaries |
| PostgreSQL 17.12 | 17.12 | Minor update: stop PostgreSQL, update binaries |
| PostgreSQL 16.16 | 16.16 | Minor update: stop PostgreSQL, update binaries |
| PostgreSQL 15.20 | 15.20 | Minor update: stop PostgreSQL, update binaries |
| PostgreSQL 14 | 14.25 | Final release, now end of life: plan a move to a supported version |
PostgreSQL 19 is not a final release yet. The project has published its second release candidate.
PostgreSQL patching checklist for this week
- Find every install. Check production, staging, containers and any app that ships with its own database. Include the machines that run pg_dump or pg_restore.
- Check the version. Connect and run
SELECT version();. If a hosting provider manages the database, ask them which minor version you are on. - Update. Stop PostgreSQL, update its binaries to the fixed version in the table and start it again. A minor release does not need a dump and reload or pg_upgrade.
- Update the backup tools. Bring the PostgreSQL tools on backup servers and laptops up to the same fixed version.
- Read the update notes. The release announcement includes a reindex step,
REINDEX INDEX your_index_name;. Before you run it, check the announcement to see whether it applies to your indexes. - Plan for 14. If you run PostgreSQL 14, patch to 14.25 now and put the major version move on the calendar.
- Confirm. Run the version check again afterward and write down the result.
Why this matters for a company website or network
The database is usually where a website or app keeps what matters most: customer records, orders and account details. A flaw that can execute arbitrary code puts everything that database holds at risk.
PostgreSQL is also often a hidden dependency. A developer may have installed it years ago, a vendor may have bundled it inside a product, or it may be running in a container nobody has touched since launch. Those are the installs most likely to be missed. If you are not sure who patches yours, read Who Is Patching the Software That Runs Your Business?. If a vendor ships PostgreSQL inside their product, Updated Is Not the Same as Patched explains why you should ask them which version they bundle.
PostgreSQL security update questions people are asking
Is CVE-2026-6460 being exploited?
The PostgreSQL pages we used do not say. Treat that as unknown, not as safe, and update anyway.
Which PostgreSQL versions fix CVE-2026-6460?
PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25. Any version before those is affected.
How severe is CVE-2026-6460?
PostgreSQL's advisory gives it a severity score of 8.8 and says it can execute arbitrary code.
How many vulnerabilities did the November 2026 PostgreSQL update fix?
The release announcement says 52 security vulnerabilities and over 140 bugs.
Do I need pg_upgrade or a dump and reload to install it?
No. It is a minor release, so you stop PostgreSQL and update its binaries.
When does PostgreSQL 14 support end?
It has ended. Version 14.25, released on November 12, 2026, is the final release, and PostgreSQL 14 will no longer receive security and bug fixes.
Do I need to run REINDEX after updating?
The announcement includes a REINDEX INDEX step. Check its update notes to see whether your indexes need it.
The bigger lesson
A database rarely shows up on anyone's screen, so it is easy to forget that it needs patches just like a website or a phone. This update fixes a long list of flaws in one maintenance window, and it is also the point where PostgreSQL 14 stops getting fixes at all. If you know what you run, which version it is and who updates it, a week like this is routine instead of a scramble.
Need help keeping your servers patched? See security hardening or request a tech quote.
Get security alerts like this by email, with our free checklist, at security alerts.
Sources: PostgreSQL Global Development Group release announcement; PostgreSQL security advisory for CVE-2026-6460.
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...
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...
ScreenConnect Vulnerability CVE-2026-84869: Exploited Flaw Runs on Technician Machines, Why Server Updates Fall Short, and Version 26.6.5
A ScreenConnect flaw, CVE-2026-84869, is being exploited, and the vulnerable code runs on the technician's mac...