PT-2026-141543
CVE-2026-6460
·
Published
2026-11-10
·
Updated
2026-11-22
Description by
CVSS 3.1
8.8
HighMetricsAV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Name of the Vulnerable Software and Affected Versions
PostgreSQL versions prior to 18.7
PostgreSQL versions prior to 17.12
PostgreSQL versions prior to 16.16
PostgreSQL versions prior to 15.20
PostgreSQL versions prior to 14.25
Description
A type confusion issue exists in the handling of composite data types (structures composed of fields with their own data types). The system failed to adequately track typed values, allowing stale values to remain in the data dictionary, PL/pgSQL variables, and other system areas. An attacker with privileges to create objects can exploit this by using
ALTER ... SET DATA TYPE or other DDL routes, such as ALTER TABLE ... ADD COLUMN; ROLLBACK; ALTER TABLE ... ADD COLUMN.Technical exploitation involves using prepared statements to create a composite type with a specific field (e.g.,
UUID), saving the query, and then using ALTER TYPE to change that field to a different type (e.g., bytea). When the prepared query is executed, the system processes the old binary representation as the new data type, leading to memory corruption and the ability to bypass ASLR. This allows the attacker to execute arbitrary code with the operating system privileges of the PostgreSQL process, potentially enabling access to confidential data and server files.Recommendations
Update to version 18.7 or later.
Update to version 17.12 or later.
Update to version 16.16 or later.
Update to version 15.20 or later.
Update to version 14.25.
Rebuild or update all installed C-language extensions to ensure they are compatible with the fix.
Rebuild indexes as required by the update.
Plan a major-version upgrade for systems running version 14, as 14.25 is the final release.
Found an issue in the description? Have something to add? Feel free to write us 👾