The bug in two sentences
PostgreSQL did not track the type of the values it handles closely enough, and those values did not carry their type with them. After anALTER TABLE … ALTER COLUMN … SET DATA TYPE, stale values could linger in the data dictionary, in PL/pgSQL variables and elsewhere: the server then reads them with the wrong type, a type confusion (CWE-843) that leads to code execution.
The PostgreSQL advisory lists other DDL routes, such as ALTER TABLE … ADD COLUMN; ROLLBACK; ALTER TABLE … ADD COLUMN.
Affected versions:
- PostgreSQL 18 before 18.7, 17 before 17.12, 16 before 16.16, 15 before 15.20;
- PostgreSQL 14 before 14.25, and every older version according to the CVE record.
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Red Hat uses the same score and rates it Important. The NVD entry carries the project’s score while awaiting its own analysis. Ubuntu gives it medium priority.
Researcher Mehmet Ince published a technical write-up on November 9, 2026. He reports triggering the crash with the least privileged login role, by creating his types in the session’s temporary schema.
The flaw is not in CISA’s Known Exploited Vulnerabilities (KEV) catalog (November 13, 2026 version), and CISA records no exploitation. The same release fixes 52 vulnerabilities, including several other 8.8 code execution flaws: one update covers them all.
Sizing your exposure
The question to ask: who can log in to your PostgreSQL server? An account that creates objects is enough. An application that creates its own tables, as most frameworks’ migrations do, holds that right.
To find the running version:
Updating PostgreSQL per distribution
A minor update needs no dump and nopg_upgrade: the project says you only need to stop PostgreSQL and update its binaries. The server must be restarted to load the fixed version.
Take a snapshot of your VPS first.
Debian
Ubuntu
As of November 17, 2026, Ubuntu is still assessing the flaw: thepostgresql-14 (22.04 LTS), postgresql-16 (24.04 LTS) and postgresql-18 (26.04 LTS) packages have no fixed version yet. Follow Ubuntu’s CVE page.
The project’s official repository, apt.postgresql.org, already ships the fixed versions for Debian 12, Debian 13, Ubuntu 22.04 and Ubuntu 24.04. If your server uses it:
RHEL and AlmaLinux
As of November 17, 2026, Red Hat lists the PostgreSQL packages of RHEL 8, 9 and 10 as under investigation: no fix is out yet for these releases. AlmaLinux follows RHEL’s fixes. The project’s official repository,download.postgresql.org, ships the fixed versions for RHEL 8, 9 and 10 and their derivatives: 18.7, 17.12, 16.16, 15.20 and 14.25. If your server uses it:
Docker and Kubernetes
The officialpostgres image on Docker Hub has carried the 18.7, 17.12, 16.16, 15.20 and 14.25 tags since November 15, 2026. Branch tags (17, for example) point to the fixed version.
C extensions
The release notes state that full protection requires rebuilding C-language extensions, and that some will need source code changes. Debian plans to rebuild its extensions in upcoming trixie point releases. An extension you compiled yourself must be rebuilt against the new PostgreSQL version. To list a database’s extensions:The update adds the
composite_type_mismatch server parameter. It can turn off the new checks, but the release notes warn that doing so carries security risks: leave it at its default value.Reducing exposure until you update
Red Hat suggests two measures to apply until the fix is installed. Restrict network access to the PostgreSQL port to trusted administration hosts. On RHEL and AlmaLinux, with firewalld:public schema from untrusted accounts:
Since PostgreSQL 15, a new database no longer grants this privilege to
PUBLIC, but a migrated or restored database keeps its original privileges. Revoking it does not cover the session’s temporary schema, the one Mehmet Ince’s write-up uses: only the update fixes the flaw.Checking the mitigation
server_version means PostgreSQL was not restarted.
Reverting the mitigation
Once the fixed version is running, give the create privilege back to the roles that need it, and only those:trusted zone must connect:

