Karen IT Security Response Center (KSRC) Advisory

Advisory ID: KSRC-2026-11174 | Publication Date: 17 November 2026

Critical Security Update for PostgreSQL
Multiple High-Severity Vulnerabilities Fixed (November 2026 Release)

Summary

The PostgreSQL Global Development Group has released a major security update addressing 52 security vulnerabilities and more than 140 bugs across all supported versions. The update includes versions 18.7, 17.12, 16.16, 15.20, 14.25, and PostgreSQL 19 RC 2.

Several of the fixed issues carry a CVSS score of 8.8 (High) and can lead to arbitrary code execution under certain conditions. Additionally, this release marks the final update for PostgreSQL 14, which is now end-of-life.

Key High-Severity Issues

Among the 52 vulnerabilities fixed, the following stand out due to their severity (CVSS 8.8) and potential impact:

  • CVE-2026-6460 – Type confusion after ALTER ... SET DATA TYPE
  • CVE-2026-18447 – Output parameter type confusion
  • CVE-2026-116304 – Parallel RECORD typmod use-after-free
  • CVE-2026-116306 – Composite-type change during field assignment
  • CVE-2026-116307 / CVE-2026-116309 / CVE-2026-116319 / CVE-2026-116320 – Multiple plperl use-after-free and type confusion issues
  • CVE-2026-116314 – pg_restore missing validation allowing arbitrary code execution
  • CVE-2026-116315 / CVE-2026-116317 – Heap buffer overflows in text search functions
  • Additional type confusion, use-after-free, and memory safety issues across core components, logical replication, and procedural languages

Many of these require an authenticated low-privilege user but can result in full code execution within the PostgreSQL process context.

Affected Versions

  • PostgreSQL 18.x → fixed in 18.7
  • PostgreSQL 17.x → fixed in 17.12
  • PostgreSQL 16.x → fixed in 16.16
  • PostgreSQL 15.x → fixed in 15.20
  • PostgreSQL 14.x → fixed in 14.25 (final release – now EOL)

Recommendations

  1. Upgrade immediately to the latest fixed version appropriate for your branch (18.7, 17.12, 16.16, or 15.20).
  2. Organizations still running PostgreSQL 14 must plan and execute a migration to a supported version as soon as possible. Version 14 will receive no further security updates.
  3. Review the official PostgreSQL release notes for any post-update steps that may be required (some fixes need additional actions after the upgrade).
  4. Prioritize internet-facing and multi-tenant database instances.
  5. After upgrading, verify the running version and monitor for unusual activity.
  6. Apply the principle of least privilege for database roles to reduce the impact of any remaining authentication-required flaws.

Given the volume and severity of the fixed issues, this update should be treated as a high-priority security release for all PostgreSQL deployments.

Support from KSRC

KSRC (Karen IT Security Response Center) is fully prepared to assist organizations with any questions, technical guidance, or incident-related issues arising from these vulnerabilities.

Whether you require help with version assessment, upgrade planning, or response coordination, our team is available.


Karen IT
We make the Internet harder to abuse.