PostgreSQL: 25 High-Severity Vulnerabilities Disclosed Together
A batch of 25 vulnerabilities in PostgreSQL, including multiple critical type confusion flaws, were disclosed on November 12, 2026, with many allowing for arbitrary code execution.

Key findings
- 25 vulnerabilities in PostgreSQL disclosed on November 12, 2026, with many allowing arbitrary code execution.
- Multiple high-severity type confusion flaws (e.g., CVE-2026-6460, CVE-2026-18447) enable RCE as the OS user.
- Several use-after-free vulnerabilities (e.g., CVE-2026-120150, CVE-2026-120147) also lead to arbitrary code execution.
- Flaws in CREATE EXTENSION (CVE-2026-6467) and INSERT ... ON CONFLICT (CVE-2026-16237) pose significant risks.
- Affected versions include releases prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25.
On November 12, 2026, a significant batch of 25 vulnerabilities affecting PostgreSQL was disclosed, with a strong emphasis on flaws leading to arbitrary code execution. The disclosures highlight critical issues such as type confusion, use-after-free, and improper access controls, many of which carry high severity ratings and allow attackers with database privileges to execute code with the operating system's user privileges.
Several vulnerabilities stem from type confusion issues. CVE-2026-6460, CVE-2026-18447, CVE-2026-120151, CVE-2026-120148, CVE-2026-120144, CVE-2026-120142, CVE-2026-116335, and CVE-2026-116331 all involve type confusion in various PostgreSQL components, including SQL-language functions, plpgsql record-field assignment, extended statistics, operator commutator and negator links, and aggregate optimization. These flaws can allow an object creator to execute arbitrary code as the operating system user running the database.
Use-after-free vulnerabilities are another prominent theme in this disclosure batch. CVE-2026-120150, CVE-2026-120147, CVE-2026-120143, CVE-2026-120152, and CVE-2026-116332 represent critical use-after-free bugs in areas such as expanded-record domain checks, the dblink extension, trigger functions, pg_show_all_settings(), and portal setup. These vulnerabilities can also lead to arbitrary code execution.
Further contributing to the risk, several CVEs involve uncontrolled search paths and improper protection mechanisms. CVE-2026-6467, an uncontrolled search path element in CREATE EXTENSION, allows for arbitrary code execution as the bootstrap superuser. CVE-2026-16237 and CVE-2026-120154 detail improper protection in INSERT ... ON CONFLICT operations, potentially allowing unauthorized data access and modification. CVE-2026-14661, an external control of file name in dblink and CREATE/ALTER SUBSCRIPTION, can lead to persistent denial of service.
Other notable vulnerabilities include CVE-2026-120149, a heap-based buffer overflow in foreign batch inserts that could allow a foreign server to execute arbitrary code. CVE-2026-120145, a missing authorization flaw in logical replication, allows a compromised publisher to execute arbitrary code. CVE-2026-116336, an operation on a dropped index during REINDEX CONCURRENTLY, also enables arbitrary code execution. Additionally, CVE-2026-120139, an integer wraparound in tuple-size calculations, and CVE-2026-116333, a buffer over-read in parallel B-tree scans, present further security risks.
According to The Hacker News, at least one of these vulnerabilities, CVE-2026-6460, has a CVSS score of 8.8 and allows for authenticated remote code execution. The report also mentions that full protection may require rebuilding C-language extensions. The affected versions for many of these vulnerabilities include versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25, indicating a broad impact across recent major releases.
PostgreSQL has released patches to address these vulnerabilities. Users are strongly advised to update to the latest available versions to mitigate the risks associated with these critical flaws. The widespread nature of these disclosures, particularly the numerous high-severity code execution bugs, underscores the importance of prompt patching and security diligence for PostgreSQL users.