CVE-2026-6472 is a medium severity vulnerability in PostgreSQL affecting versions prior to 18.4, 17.10, 16.14, 15.18, and 14.23. It involves missing authorization checks in the CREATE TYPE command, allowing an attacker who can create objects to hijack queries that rely on search_path to locate user-defined or extension-defined types. This can cause victims to execute arbitrary SQL functions chosen by the attacker. No official patch or remediation level is confirmed in the provided data.
CVE-2025-12818 is an integer overflow or wraparound vulnerability in the PostgreSQL libpq client library that can cause undersized memory allocations and out-of-bounds writes, leading to application crashes via segmentation faults. It affects multiple PostgreSQL versions prior to 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23. Exploitation requires no authentication or user interaction but has a high attack complexity due to the need for crafted input from an application input provider or network peer. The vulnerability impacts availability by causing application crashes but does not affect confidentiality or integrity.
CVE-2025-12817 is a low-severity vulnerability in PostgreSQL affecting versions prior to 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23. It involves missing authorization checks in the CREATE STATISTICS command, allowing a table owner to cause denial of service (DoS) against other users by creating statistics objects in any schema. This prevents other users with CREATE privileges from creating statistics with the same name, leading to failed operations. Exploitation requires low privileges (table owner) but no user interaction.
Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS settings to furnish arbitrary non-NUL bytes to the libpq application. For example, a man-in-the-middle attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid query results. This is probably not a concern for clients where the user interface unambiguously indicates the boundary between one error message and other text. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.
Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.
Incorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH). That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating system user. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.