On this page · 7 sections
  1. PostgreSQL 18.7 and the other minor releases: who is exposed to code execution
  2. Affected and fixed versions
  3. PostgreSQL 14 end of life
  4. Also in this release
  5. Protection steps for PostgreSQL 18, 17, 16, 15 and 14
  6. Checking PostgreSQL servers and partitioned tables after the update
  7. Sources

Security release

Status as of 2026-11-15

40 CVEs

PostgreSQL

Highest CVSS8.8High
First fixed in
14.25, 15.20, 16.16, 17.12, 18.7The earliest release on each line that fixes these CVEs. The release to install is in the article's upgrade steps.
Exploited
None known · CISA SSVC
Published
2026-11-12

Most severe first

  1. CVE-2026-116304High8.8PostgreSQL parallel RECORD typmod use-after-free executes arbitrary code
  2. CVE-2026-116306High8.8PostgreSQL composite-type change during field assignment executes arbitrary code
  3. CVE-2026-116307High8.8PostgreSQL plperl prepared-query use-after-free executes arbitrary code
  4. CVE-2026-116309High8.8PostgreSQL plperl blessed-reference type confusion may execute arbitrary code
  5. CVE-2026-116314High8.8PostgreSQL pg_restore executes arbitrary code due to missing non-plain archive validation
Show all 40 · 13 more named
  1. CVE-2026-116315High8.8PostgreSQL tsvector_delete() heap buffer overflow executes arbitrary code
  2. CVE-2026-116316High8.8PostgreSQL security-restricted operations can create types in pg_temp, which later queries of the session find
  3. CVE-2026-116317High8.8PostgreSQL ts_rank_cd() heap buffer overflow may execute arbitrary code
  4. CVE-2026-116318High8.8PostgreSQL pg_dump not-null constraint name allows SQL injection
  5. CVE-2026-116319High8.8PostgreSQL plperl reentrant return_next() use-after-free executes arbitrary code
  6. CVE-2026-116320High8.8PostgreSQL plperl array and hash conversion use-after-free executes arbitrary code
  7. CVE-2026-116323High8.8PostgreSQL pltcl reentrant result conversion use-after-free executes arbitrary code
  8. CVE-2026-116326High8.8PostgreSQL plperl tied-object exceptions follow stale sigjmp_buf
  9. CVE-2026-116329High8.8PostgreSQL statistics import type confusion executes arbitrary code
  10. CVE-2026-116331High8.8PostgreSQL min/max aggregate type confusion executes arbitrary code
  11. CVE-2026-116332High8.8PostgreSQL portal setup use-after-free executes arbitrary code
  12. CVE-2026-116335High8.8PostgreSQL commutator or negator result-type confusion executes arbitrary code
  13. CVE-2026-116336High8.8PostgreSQL REINDEX CONCURRENTLY does not block DROP INDEX during index functions
  14. CVE-2026-120141High8.8PostgreSQL materialized set-returning function type confusion executes arbitrary code
  15. CVE-2026-120142High8.8PostgreSQL dropped-column type confusion executes arbitrary code
  16. CVE-2026-120143High8.8PostgreSQL transition-table cursor use-after-free executes arbitrary code
  17. CVE-2026-120144High8.8PostgreSQL type-cache invalidation gap executes arbitrary code
  18. CVE-2026-120147High8.8PostgreSQL dblink reentrant disconnect use-after-free executes arbitrary code
  19. CVE-2026-120149High8.8PostgreSQL FDW batch-insert mismatch executes arbitrary code
  20. CVE-2026-120150High8.8PostgreSQL expanded-record domain-check use-after-free executes arbitrary code
  21. CVE-2026-120151High8.8PostgreSQL plpgsql record-field type confusion executes arbitrary code
  22. CVE-2026-18447High8.8PostgreSQL output parameter type confusion executes arbitrary code
  23. CVE-2026-6460High8.8PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code
  24. CVE-2026-120148High8.1PostgreSQL extended-statistics pseudo-type confusion executes arbitrary code
  25. CVE-2026-14661High8.1PostgreSQL dblink and subscriptions can append to arbitrary files
  26. CVE-2026-116313High7.2PostgreSQL "vacuumdb --missing-stats-only" lets a database owner execute code as the vacuumdb user
  27. CVE-2026-6467High7.2PostgreSQL extension script schema mishandling executes arbitrary SQL
  28. CVE-2026-116311Medium5.4PostgreSQL DROP OWNED can remove restrictive row security policies from non-owned tables
  29. CVE-2026-116312Medium5.4PostgreSQL MERGE can place the wrong row in a trigger transition table
  30. CVE-2026-16237Medium5.4PostgreSQL INSERT ... ON CONFLICT can read or modify rows despite auto-updatable view WHERE condition
  31. CVE-2026-116308Medium4.3PostgreSQL dict_int reads beyond zero-length tokens
  32. CVE-2026-116310Medium4.3PostgreSQL COPY error context uses freed field storage
  33. CVE-2026-116321Medium4.3PostgreSQL unterminated name value discloses server memory
  34. CVE-2026-16240Low3.7PostgreSQL pg_basebackup can use backup manifest content as a format string
  35. CVE-2026-116303Low3.1PostgreSQL foreign key and JSON conversions bypass EXECUTE privilege on cast functions

Also named in this article, without a record here: CVE-2026-116328, CVE-2026-120139, CVE-2026-120153, CVE-2026-116330, CVE-2026-116325, CVE-2026-120145, CVE-2026-120154, CVE-2026-120146, CVE-2026-120152, CVE-2026-116322, CVE-2026-116327, CVE-2026-116333, CVE-2026-6464

Data: CVE records on cve.org

Check your project

Warning

PostgreSQL versions from 18 before 18.7, from 17 before 17.12, from 16 before 16.16, from 15 before 15.20, and before 14.25 are affected by flaws fixed in the PostgreSQL 2026-11-12 release announcement, which lists 52 security vulnerabilities. Many carry a CVSS v3.1 score of 8.8 (High), assigned by PostgreSQL. Some of them, such as CVE-2026-6460 and CVE-2026-18447, allow an object creator (an authenticated database user able to create objects) to execute arbitrary code as the operating system user running the database.

PostgreSQL 18.7 and the other minor releases: who is exposed to code execution #

The announcement lists 52 CVEs, and the largest group is rated 8.8 by PostgreSQL. Several let an object creator or ordinary database user run code as the OS user of the server. Not every CVE applies to every major version, so check the CVE record for the exact range.

Type confusion in core server and SQL functions #

CVE-2026-6460 (8.8, High) is a type confusion after ALTER ... SET DATA TYPE. Other DDL routes exist, such as ALTER TABLE ... ADD COLUMN; ROLLBACK; ALTER TABLE ... ADD COLUMN. The CVE record and the PostgreSQL security page say the system had inadequate tracking of typed values, so values were not self-identifying and stale values could appear in data dictionary entries and PL/pgSQL variables. CISA's SSVC assessment rates exploitation as none.

CVE-2026-18447 (8.8) is a type confusion in SQL-language functions via an output parameter of type "any" (record).

The announcement lists more code-execution flaws rated 8.8. Type confusion: CVE-2026-116306 (composite-type change during field assignment), CVE-2026-116329 (statistics import), CVE-2026-116331 (min/max aggregates), CVE-2026-116335 (commutator or negator result type), CVE-2026-120141 (materialized set-returning function), CVE-2026-120142 (dropped column) and CVE-2026-120151 (plpgsql record field). Use-after-free: CVE-2026-116304 (parallel RECORD typmod), CVE-2026-116332 (portal setup), CVE-2026-120143 (transition-table cursor) and CVE-2026-120150 (expanded-record domain check). CVE-2026-120144 (type-cache invalidation gap) and CVE-2026-120149 (FDW batch-insert mismatch) also execute arbitrary code at 8.8. CVE-2026-116336 (8.8) is REINDEX CONCURRENTLY not blocking DROP INDEX during index functions. CVE-2026-120148 (extended-statistics pseudo-type confusion) is rated 8.1.

For plperl, the announcement lists CVE-2026-116307, CVE-2026-116309, CVE-2026-116319, CVE-2026-116320 and CVE-2026-116326, each 8.8. The CVE-2026-116309 record says a way to control the pointer was neither confirmed nor ruled out, and the project proceeds as though it is possible. CVE-2026-116323 (pltcl) and CVE-2026-120147 (dblink reentrant disconnect) are also 8.8.

Heap buffer overflows are CVE-2026-116315 (tsvector_delete()) and CVE-2026-116317 (ts_rank_cd(), via an invalid tsvector with duplicate positions), both 8.8. The announcement also lists two integer wraparounds, both 8.8: CVE-2026-116328 (generation memory context) and CVE-2026-120139 (tuple size).

Extensions, search paths and injection #

CVE-2026-6467 (7.2) lets an attacker with database-level CREATE privilege run code as the bootstrap superuser through CREATE EXTENSION, via ALTER SCHEMA ... RENAME or CREATE EXTENSION ... SCHEMA "$user"; ALTER EXTENSION was also affected (record, security page). CVE-2026-120153 (7.2) covers extension-script substitutions allowing SQL injection through object names.

CVE-2026-116316 (8.8), security-restricted operations creating types in pg_temp, lets an object creator execute arbitrary SQL as the operation's caller. The victim session must later run a query with an unqualified type name; the record says autovacuum and other common users of security-restricted operations do not, so they are unaffected.

Client tools: pg_dump, pg_restore, vacuumdb, reindexdb, pg_basebackup #

CVE-2026-116314 (8.8) lets a provider of a non-plain archive run code as the OS user running pg_restore via a crafted archive. CVE-2026-116318 (8.8, only 18 before 18.7) is SQL injection in pg_dump through a not-null constraint name; CVE-2026-116330 (8.8) is psql command injection through a pg_dump tar restore.sql. CVE-2026-116325 (reindexdb, 8.0) is SQL injection via index name quoting.

CVE-2026-116313 (7.2, 18 before 18.7 only) lets a database owner run SQL as the vacuumdb user via --missing-stats-only; the record notes that the pg_upgrade documentation recommends an affected vacuumdb invocation. CVE-2026-16240 (3.7) concerns pg_basebackup using backup manifest content as a format string: an attacker who has already compromised a server can disclose pg_basebackup memory, though the bytes are not sent back to that server, and the record says the formatter does not support %n.

File access, privileges and row security #

CVE-2026-14661 (8.1) lets dblink and CREATE/ALTER SUBSCRIPTION append NSS-keylog-format data to a chosen file through the sslkeylogfile connection parameter, causing persistent denial of service. Versions before 18 are also affected if libpq 18 or later is installed and used by the server (record, security page). CVE-2026-120145 (8.8) lets logical replication write to subscriber system catalogs, executing arbitrary code.

CVE-2026-16237 (5.4) lets someone with INSERT and UPDATE on an auto-updatable view read and modify every row in its base table via iterated INSERT ... ON CONFLICT DO UPDATE, security_barrier or not. CVE-2026-120154 (4.3) lets INSERT ... ON CONFLICT read rows despite row security policies, and CVE-2026-116311 (5.4) lets DROP OWNED remove restrictive row security policies from non-owned tables. Other privilege flaws: CVE-2026-120146 (4.3, REASSIGN OWNED bypasses role SET and CREATEDB checks) and CVE-2026-116303 (3.1, cast functions run despite missing EXECUTE privilege).

Memory disclosure and lower-severity flaws #

Disclosure of server memory is rated 4.3 for CVE-2026-116308 (dict_int), CVE-2026-116321 (unterminated name), CVE-2026-116310 (COPY error context, 17 before 17.12 and 18 before 18.7 only) and CVE-2026-120152 (pg_show_all_settings()). Others: CVE-2026-116312 (5.4, MERGE and transition tables, major versions 15 to 18 only), CVE-2026-116322 (5.3, spinlock leak on a pre-authentication cancel request), CVE-2026-116327 (4.3, security_barrier) and CVE-2026-116333 (6.5, parallel B-tree array scan).

Affected and fixed versions #

Major versionAffectedFixed in
18from 18 before 18.718.7
17from 17 before 17.1217.12
16from 16 before 16.1616.16
15from 15 before 15.2015.20
14before 14.2514.25 (final release)

Exceptions in the CVE records we checked (24 of the 52):CVE-2026-116313 and CVE-2026-116318 affect only 18 before 18.7; CVE-2026-116310 affects 17 before 17.12 and 18 before 18.7; CVE-2026-116312 affects 15 through 18; CVE-2026-14661 affects versions before 18 only if libpq 18 or later is installed and in use by the server.

PostgreSQL 14 end of life #

14.25 is the final PostgreSQL 14 release; version 14 will no longer receive security and bug fixes, and the project suggests planning an upgrade to a supported version (announcement).

Also in this release #

  • Over 140 bugs fixed; see the release notes linked from the announcement for the full list.
  • GIN index fixes for corruption that could miss or return unrelated rows; pg_trgm GiST index corruption fix; fix for missed index updates on a TOAST table after REINDEX CONCURRENTLY.
  • B-tree deduplication disabled for columns declared as bpchar without a length; char(n) is not affected.
  • NOT NULL NO INHERIT constraints disallowed on partitioned tables in all cases, including CREATE TABLE ... LIKE.
  • Fixes for incremental backups, base backups (including a torn pg_control copy), and exporting/importing snapshots on a standby.
  • Planner join removal reworked; planner, partition pruning and SQL/JSON fixes; fix for rows lost in table rewrites after an aborted subtransaction.
  • Crash-related fixes, prepared transaction state files written atomically, INSERT ... ON CONFLICT now takes a predicate lock on the conflicting row under SERIALIZABLE, a fix for MERGE with WHEN NOT MATCHED BY SOURCE when the target row is concurrently deleted, logical replication and standby fixes.
  • psql accepts multiple COPY ... FROM STDIN commands in one string again; the fix for CVE-2026-6464 had made it reject them.
  • Dump/restore fixes for views, rules, tsvector and tsquery; server no longer stuck if the startup process crashes during crash restart.
  • Time zone data updated to tzdata 2026f (Northwest Territories, Manitoba, Cuba, EST5EDT, CST6CDT, MST7MDT, PST8PDT).
  • PostgreSQL 19 RC 2: general availability is planned for November 19, 2026. It reverts allowing JSON_ARRAY() and JSON_OBJECT() over arrays, composite and range types in expression indexes, generated columns and partition keys; objects created during testing must be dropped or redefined before upgrading. It also fixes GROUPING SETS, first_value()/nth_value() loops, LISTEN/NOTIFY and hash-table sizing.

Protection steps for PostgreSQL 18, 17, 16, 15 and 14 #

  1. Update binaries to 18.7, 17.12, 16.16, 15.20 or 14.25; no dump and reload or pg_upgrade is needed, and updates are cumulative. If you are on 14, apply 14.25 now to close these CVEs, then plan a move to a supported major version, since 14.25 is the last.
  2. If a GIN index may be affected: REINDEX INDEX your_index_name;
  3. Reindex any GiST indexes using gist_trgm_ops (pg_trgm).
  4. If you see missing chunk number errors: REINDEX TABLE your_table_name;
  5. Reindex B-tree indexes on bpchar columns declared without a length.
  6. If you use incremental backups, take a new full backup and base later incrementals on it.
  7. On partitioned tables, find NOT NULL NO INHERIT constraints, then drop them with ALTER TABLE ... DROP CONSTRAINT ... or keep them with ALTER TABLE ... ALTER CONSTRAINT ... INHERIT (fails if a partition has NULLs).
  8. If you skipped earlier update releases, read their release notes for extra steps.

Checking PostgreSQL servers and partitioned tables after the update #

Compare the running server version with the table above. For partitioned tables, the announcement provides this query:

SQL
SELECT conrelid::regclass, conname
FROM pg_constraint
WHERE contype = 'n' AND connoinherit
  AND conrelid IN (SELECT oid FROM pg_class WHERE relkind = 'p');

Servers older than 18 are also exposed to CVE-2026-14661 if libpq 18 or later is installed and used by the server. Check whether you run vacuumdb --missing-stats-only (CVE-2026-116313, 18 before 18.7) and whether you use plperl, pltcl, dblink or extensions, which several of the High-rated CVEs name.

The Sentinel’s Call

Patch every supported server to its fixed minor release, including 14.25 for PostgreSQL 14, starting with databases where untrusted users can create objects or use plperl, pltcl, dblink or text search, since those carry the 8.8 ratings. Anyone on PostgreSQL 14 gets no further fixes after 14.25 and needs an upgrade plan. After updating, run the reindex steps for GIN, pg_trgm GiST, TOAST and bpchar B-tree indexes where they apply, and take a new full backup if you use incremental backups.

Our judgement, drawn only from the facts and sources above.

Verified We installed PostgreSQL 18.7, 17.12 and 16.16 from the official Docker images and ran them on Nov 14, 2026.

  • PostgreSQL 18.7 postgres --version

    postgres (PostgreSQL) 18.7 (Debian 18.7-1.pgdg13+2)

    Full output and environment
    postgres:18.7sha256:9f4fd4aa918f…
    $ postgres --version
    postgres (PostgreSQL) 18.7 (Debian 18.7-1.pgdg13+2)
  • PostgreSQL 17.12 postgres --version

    postgres (PostgreSQL) 17.12 (Debian 17.12-1.pgdg13+1)

    Full output and environment
    postgres:17.12sha256:dbb9623d5121…
    $ postgres --version
    postgres (PostgreSQL) 17.12 (Debian 17.12-1.pgdg13+1)
  • PostgreSQL 16.16 postgres --version

    postgres (PostgreSQL) 16.16 (Debian 16.16-1.pgdg13+1)

    Full output and environment
    postgres:16.16sha256:30551eca978d…
    $ postgres --version
    postgres (PostgreSQL) 16.16 (Debian 16.16-1.pgdg13+1)

Isolated container: official image, network off, read-only, no host files. How we check

Upgrade Check 18.6 → 18.7

Drop-in
PostgreSQL18.618.7
Installs and runs✓✓
No measurable differenceLoad 300,000 rows, 15,000 read-only transactions, 3,000 write transactions, GROUP BY over 300,000 rows, Sort 300,000 rows
Size on disk644.2 MB669.6 MB

Measured Nov 14, 2026 in isolated containers on 1 CPU, data in memory, pgbench scale 3, autovacuum and parallel query off, median of 11 alternating runs; differences under 10% are not reported. How we check

Sources

  1. PostgreSQL: PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released! postgresql.org · Nov 12, 2026
  2. CVE-2026-6460: PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code cve.org · Nov 12, 2026
  3. CVE-2026-6467: PostgreSQL extension script schema mishandling executes arbitrary SQL cve.org · Nov 12, 2026
  4. CVE-2026-14661: PostgreSQL dblink and subscriptions can append to arbitrary files cve.org · Nov 12, 2026
  5. CVE-2026-18447: PostgreSQL output parameter type confusion executes arbitrary code cve.org · Nov 12, 2026
  6. PostgreSQL: CVE-2026-6460: PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code postgresql.org · Reference
  7. PostgreSQL: CVE-2026-6467: PostgreSQL extension script schema mishandling executes arbitrary SQL postgresql.org · Reference
  8. PostgreSQL: CVE-2026-14661: PostgreSQL dblink and subscriptions can append to arbitrary files postgresql.org · Reference

Also consulted

More on PostgreSQL

2 other articles, newest first

Next reading

Edited and approved by Jarosław Krzemiński. Spotted a mistake? Report a correction or read the corrections policy.