Skip to content- Sources: primary, primary, primary, discussion
- Summary: The fix for CVE-2026-6460 adds versioning to composite types, turns DatumGetHeapTupleHeader() from a macro into a server function and makes heap_getattr() call a new heap_datum_check(), so PGDG rebuilt every RPM extension and now requires the matching minor release, for example postgresql18-libs >= 18.7. Jeremy Schneider reports that new AGE, credcheck and pg_cron builds already fail on 18.6 in his CloudNativePG extension pipelines, and Devrim Gunduz found a pllua crash on the new minors that PGDG patched.
- Why it matters: Anyone building or pinning extension images, as with CloudNativePG, must roll the server and extensions in lockstep or get either undefined symbol errors or unprotected extensions.
- Background: PostgreSQL extensions written in C are compiled against server headers, so macros and inline code from those headers end up inside the extension binary. The project normally keeps this binary interface stable within a major version, with rare exceptions such as 17.1. Mehmet Ince's write-up describes CVE-2026-6460 as a 22-year-old type confusion where changing a field type inside a composite type makes PostgreSQL read stored values with the wrong layout, which he turned into code execution.
- Comments: The Hacker News thread on Ince's RCE write-up drew 50 points and 6 comments.