CVE Tools

PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE

The Hacker NewsBy The Hacker News

Our summary

PostgreSQL's maintainers shipped new minor releases covering 52 security issues, headlined by a type-confusion bug that traces back 22 years and can let an authenticated user with object-creation rights execute code on the host. Tracked as CVE-2026-6460 (CVSS 8.8), the flaw stems from how composite types handle fields whose data type is altered while older values of that type still exist elsewhere in the server, letting the engine misread stale data and ultimately run attacker-supplied commands with the privileges of the OS account running PostgreSQL. No active exploitation has been reported by the project or CISA, but researcher Mehmet Ince published a technical write-up with working proof-of-concept SQL (stopping short of the final RCE step) and privately notified cloud providers including AWS, Microsoft Azure, Google AlloyDB, Supabase, Databricks and Ubicloud. Affected versions are everything before 18.7, 17.12, 16.16, 15.20 and 14.25 — the last release for the now end-of-life 14.x branch — and 32 of the 52 patched issues carry the maximum 8.8 score in this round, while a separate flaw, CVE-2026-116322, allows an unauthenticated client to crash PostgreSQL 18 servers. Administrators should update immediately and rebuild any C-language extensions alongside the server, since unrebuilt extensions may remain vulnerable, and should also patch client tools like pg_dump, pg_restore, reindexdb and vacuumdb, avoiding the new composite_type_mismatch option as a way to disable the checks.

Read at The Hacker News

The Hacker News publishes this story on its own site; we link to it rather than reprint it.

Worried this affects your company?

Discuss a security assessment of your internet-facing systems. Scope agreed before testing.

Check my exposure