The November 12 PostgreSQL security update fixes 52 security vulnerabilities across every supported version. The new releases are PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25. The most discussed flaw, CVE-2026-6460, lets a logged-in database user run code on the server. For full protection, C-language extensions also need a rebuild.
PostgreSQL sits behind many Drupal sites, Supabase projects, custom apps and association data tools. This post covers what the release fixes, who is exposed, the extra steps after you update, and what it means for managed databases on AWS and Azure. It also covers PostgreSQL 14, which got its last update in this release. Facts are as of November 16, 2026.
The short version: install the PostgreSQL security update on every server you run, and update client tools like pg_dump and pg_restore too. Rebuild any C-language extensions you compile yourself. Read the reindex steps before you close the ticket. If a cloud provider runs your database, check when it will apply the new minor version. If you are still on PostgreSQL 14, this was its final release.
What the PostgreSQL security update fixes
The PostgreSQL release announcement says the update "fixes 52 security vulnerabilities and over 140 bugs reported over the last several months." It also shipped the second release candidate of PostgreSQL 19.
The project’s security information page lists all 52 CVEs. Most affect every supported branch from 14 to 18. A few affect only 18, or 17 and 18. Many are memory bugs or type mix-ups that the project says can execute arbitrary code.
The flaws fall into a few groups:
- Server core. Most of the list. These include use-after-free bugs, type confusion bugs and buffer overflows in the database server itself.
- Procedural languages. Several affect PL/Perl and PL/Tcl, which let users write functions in those languages.
- Contrib modules. Two affect
dblink, and one affectsdict_int. - Client tools. Some affect
pg_dump,pg_restore,reindexdb,vacuumdbandpg_basebackup. For example, CVE-2026-116314 is titled "pg_restore executes arbitrary code due to missing non-plain archive validation."
That last group matters for agencies. Updating the server does not update the client tools on your laptop or build server. If you restore client database dumps, update those tools as well. Our guide to what a CVE is explains how to read entries like these.
CVE-2026-6460: the flaw getting the most attention
PostgreSQL’s CVE-2026-6460 page calls it "type confusion after ALTER … SET DATA TYPE." It scores 8.8 with CVSS 3.0. The vector shows network access, low attack complexity and low privileges needed.
The page says the flaw "allows an object creator to execute arbitrary code as the operating system user running the database." In plain terms, someone who can log in and create tables can use it to run commands on the server. Changing a column’s data type is the main route. The project says other DDL routes exist too.
The PostgreSQL 18.7 release notes explain the root cause. Rows with an older layout can linger after a type change. Past checks "were never really complete," the notes say. The fix adds version tracking so the server can spot data that no longer matches its type. The notes credit many reporters, including the OpenAI Security Research Team, the Anthropic OSS program, Claude and Ada Logics.
The Hacker News reported on November 13 that researcher Mehmet Ince traces the bug back to a May 2004 change that let PostgreSQL change a column’s type. That makes it about 22 years old. The Hacker News also says Ince shared proofs of concept privately with managed database providers, including AWS, Microsoft, Google and Supabase.
To read the score in context, see our guide to reading a CVSS score.
Is anyone exploiting these flaws?
The PostgreSQL announcement does not mention any attacks. According to The Hacker News, the project has not reported exploitation, and CISA’s CVE record lists exploitation as none. The same report says Ince’s public write-up includes SQL that crashes an unpatched server but leaves out the final step that runs a command.
That can change. A public write-up plus 52 fixes in one release gives attackers a map. Our post on EPSS explains how to track the odds of exploitation as they shift.
Who needs the PostgreSQL security update most
CVE-2026-6460 and many of the other code execution flaws need a database login. An outside visitor to your website cannot use them directly. The risk is highest where:
- Many people or apps share one server. A shared hosting box or a multi-tenant database gives every tenant a login.
- App accounts can create objects. Many CMS installs connect with a database user that owns its tables. If an attacker finds SQL injection in the app, a flaw like this could turn database access into server access. This is our reading of the risk, not a statement from the advisory.
- Untrusted dumps get restored. Several client tool flaws involve restoring dumps. Treat a dump from an unknown source like any other untrusted file.
C-language extensions need a rebuild
This step is easy to miss. The 18.7 release notes say that for full protection, the CVE-2026-6460 fix "requires rebuilding C-language extensions, and there are some extensions that will require source-code changes."
The notes also add a new server setting, composite_type_mismatch, that can turn the new checks off. PostgreSQL warns that "doing so carries security risks." Use it only to keep a broken extension running while you get a fixed build.
The Hacker News reports that the PGDG RPM maintainers warned that extensions built against older releases "may not be protected from the vulnerabilities fixed in this release." It also reports that rebuilt extensions may fail to load on older servers. So update the server and its extensions together.
In practice:
- Packaged extensions. If you install PostGIS, pgvector or similar from your distribution or the PostgreSQL package repositories, update those packages after the server. Check that new builds are available.
- Extensions you compile. Rebuild them against the new server headers and test before you deploy.
- Pure SQL extensions. The rebuild note applies to C-language extensions.
Steps after the PostgreSQL security update
The release announcement says minor releases are cumulative. You do not need to dump and reload, or run pg_upgrade. You "may simply stop PostgreSQL and update its binaries." The same announcement lists extra steps for some setups:
- GIN indexes. If you suspect a GIN index is corrupt, run
REINDEX INDEX your_index_name;. - pg_trgm. Reindex any GiST indexes that use the
gist_trgm_opsoperator class. - TOAST errors. If you see
missing chunk numbererrors, runREINDEX TABLE your_table_name;. - bpchar columns. Reindex B-tree indexes on columns declared as
bpcharwithout a length. Columns declared aschar(n)are not affected. - Incremental backups. Take a new full backup after updating and use it as the base for later incremental backups.
- Partitioned tables. The announcement gives a query to find
NOT NULL NO INHERITconstraints that need repair.
If you skipped earlier minor releases, read their release notes too. Steps from those releases may still apply.
PostgreSQL 14 got its last update
The announcement is direct: "This is the final release of PostgreSQL 14." It says version 14 "is now end-of-life and will no longer receive security and bug fixes." The 14.25 release notes word it more softly, calling it "expected to be the last" 14.x release.
The PostgreSQL versioning policy lists November 12, 2026 as version 14’s final release date. Version 15 is next, with a final release planned for November 11, 2027.
Install 14.25 now, because this PostgreSQL security update carries the CVE-2026-6460 fix. Then plan a major upgrade. Our post on PostgreSQL 14 end of life covers the cloud provider deadlines and the upgrade paths.
Managed databases: when AWS and Azure apply it
If a cloud provider runs your database, you cannot install the PostgreSQL security update yourself. The provider ships its own build on its own schedule. Here is what two large providers publish, as of November 16, 2026.
| Provider | How minor updates arrive | PostgreSQL 14 standard support ends |
|---|---|---|
| Amazon RDS for PostgreSQL | AWS targets new minor versions “within 7 days of the community release.” Its calendar did not yet list 18.7 or 17.12 when we checked. | February 28, 2027, then paid Extended Support |
| Azure Database for PostgreSQL flexible server | Automatic during your maintenance window, rolled out region by region | January 31, 2027, then Extended Support options |
The RDS details come from the Amazon RDS for PostgreSQL release calendar. Its newest entries, 18.6 and its siblings, came out on RDS on August 25, 2026. That was 12 days after the community release on August 13.
The Azure details come from Microsoft’s version policy for Azure Database for PostgreSQL. It says servers update "during its configured maintenance window, after the update reaches the region that hosts the server." Keep a valid maintenance window set.
For Google Cloud SQL, Supabase and other hosts, check their release notes or status pages. Read the provider’s notice before you assume the fix is in.
How to check your PostgreSQL version
Connect with psql or your admin tool and run SELECT version(); or SHOW server_version;. These are standard PostgreSQL commands, not steps from the advisory. The PostgreSQL security update is in place if you see one of these versions or later:
- 18.7
- 17.12
- 16.16
- 15.20
- 14.25
Linux packages can add a suffix to the version string. The PostgreSQL number at the start is what counts.
To list your extensions, run SELECT extname, extversion FROM pg_extension; in each database. That shows what may need a rebuild or a package update. On the client side, run pg_dump --version on every machine that takes or restores backups.
Drupal and other apps on PostgreSQL
Drupal runs on PostgreSQL as well as MySQL and MariaDB. Drupal’s database requirements page lists PostgreSQL 12 or later for Drupal 10, 16 or later for Drupal 11, and 18 or later for Drupal 12. It also requires the pg_trgm extension. That makes the gist_trgm_ops reindex step worth checking on Drupal databases. This query lists those indexes: SELECT indexname FROM pg_indexes WHERE indexdef LIKE '%gist_trgm_ops%';.
Drupal 10 on PostgreSQL has two deadlines now. Drupal 10 itself reaches end of life on December 9, 2026, as our Drupal 10 end-of-life guide explains. A site on Drupal 10 and PostgreSQL 14 runs two unsupported layers at once by year end.
Apps built on Supabase run on PostgreSQL that Supabase manages. Check Supabase’s own notices for when the fix lands. Custom apps, CRMs and data tools that use PostgreSQL follow the same rule. Whoever runs the server needs to apply this PostgreSQL security update and rebuild extensions.
Frequently Asked Questions
Which versions include the PostgreSQL security update?
PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25, released November 12, 2026. Any earlier minor release of a supported branch is missing the fixes.
How many vulnerabilities does it fix?
The PostgreSQL project says 52 security vulnerabilities and over 140 other bugs. Its security page lists each CVE with a score.
What is CVE-2026-6460?
A type confusion flaw after ALTER … SET DATA TYPE. PostgreSQL says it lets a user who can create objects run code as the operating system user that runs the database. It scores 8.8.
Can someone exploit CVE-2026-6460 without a login?
No. It needs a database account that can create objects. The risk is highest on shared servers and where an app’s database user owns its tables.
Is CVE-2026-6460 being exploited?
No attacks were reported as of November 16, 2026. The Hacker News says CISA’s CVE record lists exploitation as none. A public write-up exists, so patch soon.
Do I need to rebuild extensions after the PostgreSQL security update?
Yes, for C-language extensions. PostgreSQL’s release notes say full protection requires rebuilding them, and some need source-code changes. Update packaged extensions after the server.
Do I need pg_upgrade or a dump and restore?
No. This is a minor release. Stop PostgreSQL, update the binaries and restart. Then run any reindex or backup steps that apply.
Is PostgreSQL 14 still supported?
No. The announcement calls 14.25 the final release of PostgreSQL 14. Install 14.25 for this fix, then plan an upgrade to a newer major version.
When will AWS RDS or Azure get the fix?
AWS targets new minor versions within 7 days of the community release. Azure applies them automatically in your maintenance window, region by region. Check each provider’s notices.
Does this PostgreSQL security update affect Drupal sites?
Yes, if the site uses PostgreSQL. Drupal requires the pg_trgm extension, so check for GiST indexes that use gist_trgm_ops and reindex them after updating.