A vulnerability in PostgreSQL's REINDEX CONCURRENTLY operation on a dropped index allows an object creator to execute arbitrary code as the operating system user running the database. This issue affects versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25. The flaw arises from an index expression that issues DROP INDEX, enabling code execution.
A use-after-free vulnerability in the PostgreSQL portal setup allows an object creator to execute arbitrary code with the privileges of the operating system user running the database. This occurs when user-defined code runs during planning or executor startup and closes the portal currently being prepared. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
A type confusion vulnerability exists in PostgreSQL materialized set-returning functions, including json_populate_recordset(), that allows a database user to execute arbitrary code with the privileges of the operating system user running the database. This affects PostgreSQL versions prior to 18.7, 17.12, 16.16, 15.20, and 14.25. The vulnerability is classified as high severity with a CVSS score of 8.8.
A type confusion vulnerability in PostgreSQL's min/max aggregate optimization allows an object creator to execute arbitrary code with the privileges of the operating system user running the database. This occurs when a user-defined aggregate uses the SORTOP option, causing the planner to treat the aggregate's input and result as the same type even when they differ. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
An integer wraparound vulnerability in PostgreSQL's in-memory tuple-size calculations allows a database user with limited privileges to execute arbitrary code with the operating system privileges of the database process. This affects PostgreSQL versions prior to 18.7, 17.12, 16.16, 15.20, and 14.25. The vulnerability has a high severity with a CVSS score of 8.8.
A type confusion vulnerability in PostgreSQL operator commutator and negator links allows an object creator with privileges to execute arbitrary code as the operating system user running the database. This occurs via linking operators that have different result types or by creating inconsistent reciprocal links. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
A vulnerability in PostgreSQL's pg_dump tar-format restore.sql allows a compromised origin server to execute arbitrary code as the client OS user running psql. This issue arises from untrusted data inclusion via a predictable restriction key in restore.sql, which is undocumented. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
A vulnerability in PostgreSQL security_barrier processing allows a database user with limited privileges to infer sensitive information that should be hidden by a security_barrier view. This occurs by applying a leaky function to a CASE test value or internal parameter indirectly representing a protected column. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
A vulnerability in PostgreSQL prior to versions 18.7, 17.12, 16.16, 15.20, and 14.25 allows an object creator to execute arbitrary SQL as the caller of a security-restricted operation. This occurs due to improper protection of an alternate path involving domain, enum, or range types created in the temporary schema pg_temp. The exploit requires the victim session to run a query with an unqualified type name, which common security-restricted operations like autovacuum do not perform.
A heap-based buffer overflow vulnerability exists in the PostgreSQL function tsvector_delete(). This flaw allows a database user with limited privileges to execute arbitrary code with the operating system user privileges running the database. The issue arises when processing a tsvector containing lexeme data with a nonstandard but valid ordering that triggers additional alignment padding. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. The vulnerability has a high severity score of 8.8 and impacts confidentiality, integrity, and availability.
A heap-based buffer overflow vulnerability exists in the ts_rank_cd() function of PostgreSQL. This flaw may allow a database user to execute arbitrary code with the privileges of the operating system user running the database. The vulnerability is triggered by an invalid tsvector containing duplicate positions. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
A use-after-free vulnerability exists in the PostgreSQL pltcl extension that allows an object creator to execute arbitrary code as the operating system user running the database. This occurs via a domain CHECK constraint that re-enters the Tcl interpreter and manipulates a string that is still in use during result conversion. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
A vulnerability in PostgreSQL prior to versions 18.7, 17.12, 16.16, 15.20, and 14.25 allows a database user to disclose server memory due to improper null termination in array element assignment. This occurs when the final byte of a fixed-length name value is changed to a nonzero byte and then processed as a C string.
A use-after-free vulnerability exists in the PostgreSQL plperl procedural language component. This flaw allows an object creator to execute arbitrary code with the privileges of the operating system user running the database. The vulnerability is triggered via reentrant return_next() calls. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
A use-after-free vulnerability exists in the PostgreSQL plperl procedural language, allowing an object creator to execute arbitrary code as the operating system user running the database. This occurs when the final reference to a Perl array or hash is dropped during PostgreSQL's object conversion process. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
Uncaught exceptions in the PostgreSQL plperl procedural language handler can lead to use of a stale sigjmp_buf when an object creator uses a tied Perl object or a Perl object whose overloaded conversion throws during error handling. This flaw affects PostgreSQL versions prior to 18.7, 17.12, 16.16, 15.20, and 14.25. The vulnerability has a high severity with a CVSS score of 8.8 and may allow arbitrary code execution on some platforms.
A type confusion vulnerability in PostgreSQL's plperl procedural language allows an object creator to execute arbitrary code by blessing a non-hash reference into PostgreSQL::InServer::ARRAY. This affects PostgreSQL versions prior to 18.7, 17.12, 16.16, 15.20, and 14.25. The vulnerability has a high severity with a CVSS score of 8.8. It is not confirmed whether the pointer can be controlled sufficiently to achieve full security impact, but the issue is treated as potentially exploitable.
A vulnerability in PostgreSQL's pg_restore utility allows arbitrary code execution due to improper input validation of non-plain archive providers. This flaw affects versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25. The issue enables an attacker to execute code as the operating system user running pg_restore by supplying a crafted archive. This is distinct from arbitrary SQL execution during restore, as it impacts the OS process itself.
A use-after-free vulnerability exists in PostgreSQL's handling of anonymous RECORD type identifiers among parallel workers. This flaw allows a database user to execute arbitrary code with the privileges of the operating system user running the database. The issue arises when one process frees a shared tuple descriptor while another process still retains and later uses its address. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
A type confusion vulnerability in PostgreSQL composite-value field assignment allows an object creator to execute arbitrary code with the privileges of the operating system user running the database. This occurs by changing a composite type between deforming and reforming a value. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.