PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE
About 2 min read
PostgreSQL’s development team rolled out a batch of security updates yesterday that close 52 vulnerabilities, the most serious of which is a type‑confusion flaw (CVE‑2026‑6460) that could let a database user who can create objects execute arbitrary code on the host server. The bug carries an 8.8 CVSS severity rating and, if exploited, runs with the same operating‑system privileges as the PostgreSQL process.
The fix applies to every release older than 18.7, 17.12, 16.16, 15.20 and 14.25, meaning a broad swath of installations are at risk. The vulnerability is triggered when a user with object‑creation rights alters the definition of a composite type while older values of that type still exist elsewhere in the system. The server could then interpret those stale values as the new type, leading to a crash that can be escalated to code execution. The patch introduces version checks that detect mismatched values, and full remediation also requires rebuilding any C‑language extensions that have been compiled for the server.
Security researcher Mehmet Ince demonstrated a working exploit against PostgreSQL 18.6 in a technical write‑up released this week. His method involves inserting a value, changing the type of one of its fields, and then re‑executing the query to cause a crash and leak memory addresses. Although the final step that actually runs a command is omitted, Ince notes that the crash can be triggered even by the lowest‑privileged login role. The PostgreSQL Global Development Group’s advisory describes the attacker simply as someone able to create or modify objects, while Red Hat’s CVE assessment adds that a database login with those capabilities is required. No incidents have been reported, and the CISA entry lists exploitation as “none.”
The flaw’s origins trace back to a change made on May 5 2004 that allowed column‑type alterations, with the exploit technique relying on a subsequent modification introduced on May 14 2015. Ince also adapted the attack for several managed PostgreSQL services and privately shared proofs of concept with the security teams of AWS (Aurora and RDS), Microsoft Azure PostgreSQL, Google AlloyDB, Supabase, Databricks and Ubicloud in August; the current patch status of those providers was not disclosed.
Among the 52 fixes, 32 receive the top‑score rating of 8.8. Only one vulnerability (CVE‑2026‑116322) can be triggered without any login, allowing an unauthenticated client to force a restart of PostgreSQL 18 servers. Additional client‑tool patches address issues where crafted archives could cause pg_restore or psql to execute code under the invoking user’s account. Administrators are urged to apply the updates immediately and rebuild any C‑language extensions to ensure complete protection.
United Launch Alliance’s (ULA) Vulcan rocket suffered a catastrophic failure minutes after liftoff on Sunday, sending 40 of Amazon’s Leo broadband satellites back to Earth. The mishap, which…
**Xbox Announces Project Helix: A New Console That Plays PC Games** Xbox has officially confirmed that its upcoming Project Helix is a console designed to run games from a PC. The announceme…
Microsoft has announced that the Xbox Series X/S and Xbox One will receive a set of new boot‑up options as part of a recent software update. The company’s statement highlighted that the upda…