PostgreSQL patches 52 flaws; version 14 reaches end of life
PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 fix 52 flaws, including CVE-2026-6460; update servers, client tools and C extensions.
- Published
- Updated
- Ecosystem
- Open sourceCloud
- Fixed in
- PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25 (14.25 is the last release of version 14)
- Exploitation
- No, the project has reported no attacks and the CVE record lists exploitation as none, but a researcher has published a partial exploit writeup
Live scores
CVE-2026-6460- EPSS
- 0.006
low predicted chance of attack - VEDAS
- 0.953
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-6467- EPSS
- 0.006
low predicted chance of attack - VEDAS
- 0.047
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-116322- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.053
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
What happened
The PostgreSQL Global Development Group released PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 on November 12. Help Net Security reports that the release fixes 52 security vulnerabilities and more than 140 other bugs Help Net Security. It says 32 of the 52 CVEs carry a CVSS score of 8.8, the highest in the batch, and the lowest scores 3.1.
The headline flaw is CVE-2026-6460, a type confusion bug in the core server with a CVSS score of 8.8. The Hacker News reports that a database user who can create objects can run code on the server with the rights of the operating system user that runs PostgreSQL The Hacker News. It involves composite types: a field’s type can be changed while older values of that type are still held elsewhere, so the server may read an old value as the new type. The fix adds version checks to detect such values. kylesinvestigation.com, summarising the PostgreSQL advisory, says the primary route is ALTER ... SET DATA TYPE, and that other DDL sequences can also trigger it kylesinvestigation.com.
Other details from the reporting:
- Age of the bug: The Hacker News says researcher Mehmet Ince traces the root to May 5, 2004. kylesinvestigation.com says press coverage puts the flaw at more than 20 years old.
- Exploitation: The Hacker News says the project has reported no attacks and that CISA’s assessment in the CVE record lists exploitation as none. It also says Ince published a writeup, demonstrated on PostgreSQL 18.6, that includes the SQL for a crash and a memory address leak but not the final step that runs a command.
- Privileges needed: Ince wrote that he could trigger the crash as a lowest-privileged login role. The Hacker News notes that none of its sources says whether an account with only default privileges can go beyond the crash to run code.
- Pre-auth flaw: The Hacker News says that, by the project’s scores, only one server flaw needs neither a login nor user action: CVE-2026-116322, which lets an unauthenticated client trigger a restart of PostgreSQL 18 servers.
- Other CVE: kylesinvestigation.com lists CVE-2026-6467, where mishandling of extension script schemas can lead to arbitrary SQL execution (CVSS 7.2).
- Bug classes: Help Net Security says most of the code execution bugs are memory errors or type confusion, in PL/Perl, PL/Tcl, text search functions such as ts_rank_cd(), parallel query, logical replication, dblink and statistics import.
- Client tools: Help Net Security reports a SQL injection in pg_dump through not-null constraint names, a tar-format restore script that failed to block psql command injection, and mishandled quoting of index names in reindexdb. The Hacker News adds that a crafted archive can make pg_restore run code as the user running it.
- Managed services: The Hacker News says Ince privately shared proofs of concept in August with security teams at AWS (Aurora and RDS), Microsoft (Azure PostgreSQL), Google (AlloyDB), Supabase, Databricks and Ubicloud. The current patch status of each service is not confirmed.
Version 14.25 is the final release of PostgreSQL 14, which gets no further security or bug fixes Help Net Security. The project also shipped PostgreSQL 19 RC 2, with general availability planned for November 19.
Am I affected?
- Server versions: The Hacker News says all versions before 18.7, 17.12, 16.16, 15.20 and 14.25 are affected by CVE-2026-6460. kylesinvestigation.com says this covers every supported major version, 14 through 18.
- Who can reach the bug: Per kylesinvestigation.com, attackers need a valid login with object-creation privileges. The Hacker News says Red Hat’s assessment requires a login able to create or modify objects.
- C-language extensions: The Hacker News quotes a notice from the project’s RPM package maintainers that extensions built against older releases still load but “may not be protected from the vulnerabilities fixed in this release.”
- Client tools: Help Net Security says that if you run pg_dump, pg_restore, reindexdb and similar tools against databases where other users can create and name objects, you should update the client binaries as well.
- PostgreSQL 14: It is end-of-life with this release. The Hacker News says older major versions are also affected and received no update.
- PostgreSQL 19 RC 2 testers: Help Net Security says RC 2 reverts support for JSON_ARRAY() and JSON_OBJECT() over arrays, composite types and range types in expression indexes, generated columns and partition keys. Objects built that way must be dropped or redefined before upgrading.
What to do now
- Update the server to 18.7, 17.12, 16.16, 15.20 or 14.25, matching your major version. kylesinvestigation.com says minor releases are cumulative, so no dump and reload is needed.
- Rebuild or update every C-language extension at the same time as the server. The Hacker News says some extensions will also need source-code changes, and that extensions rebuilt for the new releases can fail to load on older servers.
- If PostgreSQL runs outside its package’s own service unit, for example under Patroni, restart it right after updating, according to a maintainer of the RPM packages cited by The Hacker News.
- Update client tools such as pg_dump, pg_restore, psql, reindexdb and vacuumdb on every machine that runs them, including backup servers and admin workstations.
- After updating, reindex where Help Net Security says it is needed:
- GIN indexes suspected of corruption.
- pg_trgm GiST indexes that use gist_trgm_ops.
- B-tree indexes on bpchar columns declared without a length.
- REINDEX TABLE for tables that throw “missing chunk number” errors.
- If you use incremental backups, take a new full backup and base later incrementals on it, because several fixed bugs could produce corrupt backups Help Net Security.
- Review who holds object-creation privileges such as CREATE on schemas and databases, since kylesinvestigation.com identifies those users as the ones who can reach the CVE-2026-6460 path.
- Do not disable the new composite_type_mismatch checks; the project says doing so carries security risks. The Hacker News says the project’s advisory and release notes offer no workaround for servers that cannot be updated yet.
- If you still run PostgreSQL 14, plan a move to a supported major version.
Update, 15 November 2026
- The Hacker News says Mehmet Ince’s technique for running code relies on a later PostgreSQL change made on May 14, 2015, not only on the 2004 change that added the ability to change a column’s type. (thehackernews.com)
- The Hacker News says the project credits more than a dozen reporters for CVE-2026-6460, including Ince, and credits him on five other flaws in the same release. (thehackernews.com)
- The Hacker News says extension packages in the project’s RPM repositories now require the new minor release. (thehackernews.com)
Sources
- Help Net Security: PostgreSQL security update fixes 52 vulnerabilities, ends support for PostgreSQL 14
- The Hacker News: PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE
- kylesinvestigation.com: PostgreSQL Patches 52 Vulnerabilities, Including a Code Execution Flaw That Reportedly Dates Back Two Decades