ELS Builds for the November PostgreSQL Fixes Are Available
Patched PostgreSQL builds for end of life versions have been in the TuxCare repositories since November 15, three days after the upstream release.
ELS status: The builds cover PostgreSQL 8.4 through 14 in ELS for Operating Systems and ELS for PostgreSQL, and each includes the High-severity fixes applicable to its version. CVE-2026-6460 is fixed in PostgreSQL 14 on EL9. Versions below 14 have a partial fix with the changes that can be safely applied, so customers on those versions should also limit who can log in to the database to reduce the remaining risk. Fixes for the Medium and Low-severity vulnerabilities will follow within 48 hours, and their status can be checked in the TuxCare CVE tracker.
Key Takeaways
- PostgreSQL released versions 18.7, 17.12, 16.16, 15.20, and 14.25 on November 12 to fix 52 vulnerabilities.
- The most serious of them, CVE-2026-6460, lets a database user who can create objects run code on the server.
- The upstream fixes end with PostgreSQL 14; 14.25 is its final release, so versions 13 and earlier received no updates.
- TuxCare released builds with the High-severity fixes for PostgreSQL 8.4 through 14 on November 15.
- In those builds, CVE-2026-6460 is fixed in PostgreSQL 14 on EL9 and partially fixed in versions below 14, where limiting database logins reduces the remaining risk.
The PostgreSQL project published its November 2026 PostgreSQL security updates on November 12. Versions 18.7, 17.12, 16.16, 15.20, and 14.25 fix 52 vulnerabilities, and 32 of them carry a CVSS score of 8.8, the highest in the release.
The most serious one, CVE-2026-6460, allows a database user who can create objects to run code on the server, and a researcher has published a write-up showing a working exploit. Teams on a supported version can update to the new minor release. Teams on a version that upstream no longer maintains need the fixes backported, and TuxCare released Endless Lifecycle Support (ELS) builds with the High-severity fixes on November 15.
PostgreSQL 13 and older have the same vulnerabilities and no upstream fix
PostgreSQL 14.25 is the final release of PostgreSQL 14, which the project’s announcement now lists as end of life. Version 13 reached that point a year earlier under the project’s versioning policy, so the November release contains nothing for 13 or any older version. Some of the vulnerable code exists there too, and our source audit found CVE-2026-6460 in every version we support, back to PostgreSQL 8.4.
The vulnerabilities also reach beyond the database server. Three of the 8.8-rated ones are in pg_dump and pg_restore, including CVE-2026-116314, where a crafted archive makes pg_restore run code as the user who started it. The client tools therefore need the update on every machine that runs backups or restores, including machines that don’t host a database.
CVE-2026-6460 lets a database user run code on the server
The PostgreSQL advisory describes CVE-2026-6460 as a type confusion vulnerability that allows a user who can create database objects to execute arbitrary code as the operating system user running the database. The attack changes the data type of a column or of a composite type’s attribute while the server still holds values stored under the old type. PostgreSQL then reads those bytes as the new type.
Mehmet Ince, one of the researchers credited with the report, published a technical write-up on November 9 that demonstrates the exploit on PostgreSQL 18.6. He traces the underlying behavior to a commit from May 2004 and says a login role with the lowest privileges can crash the server.
According to The Hacker News, the write-up does not include the commands for the final step, the one that runs code on the server, and as of November 13 the PostgreSQL project had reported no attacks using the vulnerability. A database that accepts logins from application accounts, contractors, or tenants is exposed to this vulnerability because the attacker needs only an account that can create objects.
TuxCare released builds for end of life PostgreSQL on November 15
TuxCare engineers started the backport on November 15 and released the first patched build, PostgreSQL 14 for EL9, at 13:26 UTC. The last build reached the TuxCare repositories at 23:02 UTC the same day. The work that day covered the High-severity vulnerabilities, meaning those with a CVSS score of 7.0 or higher. Several of them are in features that older versions don’t have, so each build includes fixes for the vulnerabilities present in its version.
ELS for PostgreSQL provides security fixes for PostgreSQL versions that have reached end of life, delivered via a TuxCare repository. ELS for Operating Systems provides security updates for Linux distributions past end of life or standard vendor support, including the PostgreSQL packages that ship with them.
| Product | PostgreSQL version | Operating systems |
|---|---|---|
| ELS for PostgreSQL | 14 | EL9 |
| ELS for PostgreSQL | 13 | Ubuntu 22.04 |
| ELS for PostgreSQL | 11, 9.6 | EL7 |
| ELS for OS | 13 | RHEL 8, AlmaLinux 9.2, 9.6, and 9.8 (ESU) |
| ELS for OS | 12 | Ubuntu 20.04 |
| ELS for OS | 11, 9.6 | Debian 10 |
| ELS for OS | 10 | Ubuntu 18.04 |
| ELS for OS | 9.5 | Ubuntu 16.04 |
| ELS for OS | 9.2 | CentOS 7, RHEL 7, Oracle Linux 7, CloudLinux 7, Amazon Linux 2 |
| ELS for OS | 8.4 | CentOS 6, Oracle Linux 6 |
Fixes for the Medium- and Low-severity vulnerabilities in the November release are in progress and will be pushed to the same repositories within 48 hours. Their status can be checked in the TuxCare CVE tracker.
Versions below PostgreSQL 14 have a partial CVE-2026-6460 fix, so limit who can log in
The upstream fix for CVE-2026-6460 is large. It adds version tracking to composite type values so the server can detect a value that no longer matches its type, along with new locking and dependency checks around type changes. TuxCare rebased ELS for PostgreSQL 14 on EL9 to upstream 14.25, so that the build contains the complete fix.
For PostgreSQL versions below 14, TuxCare backported the portion of the CVE-2026-6460 fix that can be safely applied to the older code. Those builds include the dependency checks and locking that upstream added in response to type changes. They do not include version tracking, so on these versions, the vulnerability is partially mitigated.
The attack requires a database login, so customers on PostgreSQL versions older than 14 can reduce the remaining risk by limiting who can log in to the database. In practice, that means removing unused roles and restricting network access to the database port to the hosts that need it.
What to do after the packages are installed
Servers already subscribed to ELS for OS or ELS for PostgreSQL receive the builds through the package manager they use today. The running server continues to use the old binaries until PostgreSQL restarts, so plan a restart once the packages are installed. Update the client packages on any machine that runs pg_dump or pg_restore as well.
A backported build keeps its original PostgreSQL version number, so a scanner that reads only the version string may report the server as vulnerable. TuxCare publishes machine-readable security data for its ELS builds, including CSAF and VEX, so a scanner that reads those formats can see which CVEs a build has fixed. The CVE tracker shows the status of each CVE for each product. Teams on PostgreSQL versions below 14 should also review login access now, as this control reduces the remaining risk from CVE-2026-6460.
Get ELS for OS on EOL operating systems and ELS for PostgreSQL →
References
PostgreSQL, PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released
PostgreSQL, CVE-2026-6460 security advisory
PostgreSQL, Release 18.7 notes
Mehmet Ince, How I Ended Up Turning a 22-Year-Old PostgreSQL Type-Confusion Primitive into RCE (CVE-2026-6460)
The Hacker News, PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE
TuxCare, ELS for PostgreSQL documentation