The NetBSD Project

CVS log for pkgsrc/databases/postgresql18/distinfo

[BACK] Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql18

Request diff between arbitrary revisions


Keyword substitution: kv
Default branch: MAIN


Revision 1.7: download - view: text, markup, annotated - select for diffs
Fri Nov 13 12:42:44 2026 UTC (2 days, 19 hours ago) by adam
Branches: MAIN
CVS tags: HEAD
Diff to: previous 1.6: preferred, colored
Changes since revision 1.6: +4 -4 lines
postgresql1[4-8]: updated to 18.7, 17.12, 16.16, 15.20, 14.25

18.7, 17.12, 16.16, 15.20, 14.25

Security Issues

The following security vulnerabilities are closed in this update release. You can find more details about the vulnerabilities and their affected versions in the links below:

CVE-2026-6460: Type confusion after ALTER ... SET DATA TYPE executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-6467: Extension script schema mishandling executes arbitrary SQL (CVSS v3.1: 7.2)
CVE-2026-14661: dblink and subscriptions can append to arbitrary files (CVSS v3.1: 8.1)
CVE-2026-16237: INSERT ... ON CONFLICT can read or modify rows despite auto-updatable view WHERE condition (CVSS v3.1: 5.4)
CVE-2026-16240: pg_basebackup can use backup manifest content as a format string (CVSS v3.1: 3.7)
CVE-2026-18447: Output parameter type confusion executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116303: Foreign key and JSON conversions bypass EXECUTE privilege on cast functions (CVSS v3.1: 3.1)
CVE-2026-116304: Parallel RECORD typmod use-after-free executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116306: Composite-type change during field assignment executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116307: plperl prepared-query use-after-free executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116308: dict_int reads beyond zero-length tokens (CVSS v3.1: 4.3)
CVE-2026-116309: plperl blessed-reference type confusion may execute arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116310: COPY error context uses freed field storage (CVSS v3.1: 4.3)
CVE-2026-116311: DROP OWNED can remove restrictive row security policies from non-owned tables (CVSS v3.1: 5.4)
CVE-2026-116312: MERGE can place the wrong row in a trigger transition table (CVSS v3.1: 5.4)
CVE-2026-116313: vacuumdb --missing-stats-only lets a database owner execute code as the vacuumdb user (CVSS v3.1: 7.2)
CVE-2026-116314: pg_restore executes arbitrary code due to missing non-plain archive validation (CVSS v3.1: 8.8)
CVE-2026-116315: tsvector_delete() heap buffer overflow executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116316: Security-restricted operations can create types in pg_temp, which later queries of the session find (CVSS v3.1: 8.8)
CVE-2026-116317: ts_rank_cd() heap buffer overflow may execute arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116318: pg_dump not-null constraint name allows SQL injection (CVSS v3.1: 8.8)
CVE-2026-116319: plperl reentrant return_next() use-after-free executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116320: plperl array and hash conversion use-after-free executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116321: Unterminated name value discloses server memory (CVSS v3.1: 4.3)
CVE-2026-116322: Pre-authentication cancel request can leak a spinlock (CVSS v3.1: 5.3)
CVE-2026-116323: pltcl reentrant result conversion use-after-free executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116325: reindexdb index name quoting allows SQL injection (CVSS v3.1: 8)
CVE-2026-116326: plperl tied-object exceptions follow stale sigjmp_buf (CVSS v3.1: 8.8)
CVE-2026-116327: security_barrier analysis can expose hidden values through indirect expressions (CVSS v3.1: 4.3)
CVE-2026-116328: Generation memory context integer wraparound executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116329: Statistics import type confusion executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116330: pg_dump tar restore.sql fails to block psql command injection (CVSS v3.1: 8.8)
CVE-2026-116331: Min/max aggregate type confusion executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116332: Portal setup use-after-free executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116333: Parallel B-tree array scan reads beyond array bounds (CVSS v3.1: 6.5)
CVE-2026-116335: Commutator or negator result-type confusion executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-116336: REINDEX CONCURRENTLY does not block DROP INDEX during index functions (CVSS v3.1: 8.8)
CVE-2026-120139: Tuple-size integer wraparound executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-120141: Materialized set-returning function type confusion executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-120142: Dropped-column type confusion executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-120143: Transition-table cursor use-after-free executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-120144: Type-cache invalidation gap executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-120145: Logical replication can write to subscriber system catalogs, executing arbitrary code (CVSS v3.1: 8.8)
CVE-2026-120146: REASSIGN OWNED bypasses role SET and CREATEDB checks (CVSS v3.1: 4.3)
CVE-2026-120147: dblink reentrant disconnect use-after-free executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-120148: Extended-statistics pseudo-type confusion executes arbitrary code (CVSS v3.1: 8.1)
CVE-2026-120149: FDW batch-insert mismatch executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-120150: Expanded-record domain-check use-after-free executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-120151: plpgsql record-field type confusion executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-120152: pg_show_all_settings() use-after-free discloses memory (CVSS v3.1: 4.3)
CVE-2026-120153: Extension-script substitutions allow SQL injection through object names (CVSS v3.1: 7.2)
CVE-2026-120154: INSERT ... ON CONFLICT can read rows despite row security policies (CVSS v3.1: 4.3)

Bug Fixes and Improvements

This update fixes over 140 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 18. Many of these issues also affect other supported versions of PostgreSQL.

Fix exporting and importing snapshots taken on a standby server. The issue was detected when running a parallel pg_dump against a standby server, and could corrupt both the dump output and the standby server's data. More generally, a transaction that imported a snapshot taken on a standby server could return wrong results.
Several fixes for GIN indexes that could lead to index corruption, causing queries to miss rows or to return unrelated rows. If you suspect a GIN index is affected, you should reindex it. See the release notes for more details on the issue, and the "Updating" section for post-update steps.
Fix possible index corruption in pg_trgm GiST indexes that could cause searches to miss matching rows. You need to reindex after updating; see the "Updating" section.
Fix a case where, after REINDEX CONCURRENTLY rebuilt an index on a TOAST table, later index updates could be missed, leading to missing chunk number errors. If you've encountered this issue, after updating, you'll need to reindex. See the "Updating" section.
Disallow NOT NULL NO INHERIT constraints on partitioned tables in all cases, including CREATE TABLE ... LIKE. Previously, this could allow a partition to contain NULL values when it should not. See the "Updating" section for how to find and repair affected constraints.
Disable B-tree index deduplication for columns declared as bpchar without a length, which could cause index-only scans to return wrong results. If you have B-tree indexes on bpchar columns, you should reindex them after updating. See the "Updating" section.
Several fixes for incremental backups that could produce corrupt backups. We recommend taking a new full backup after updating and using it for subsequent incremental backups. See the "Updating" section.
Several fixes for base backups, including avoiding a torn copy of the pg_control file, and avoiding truncated or zero-padded copies of files such as postgresql.auto.conf that are replaced while the backup is running.
Rework the planner's join removal implementation. While this is a significant change for an update release, it was made to avoid continued bugs from the previous implementation.
Fix possible loss of rows during a table rewrite (for example, CLUSTER or VACUUM FULL) when a row had been updated by a subtransaction that later aborted.
Fix parallel vacuum I/O timing reports.
Several fixes that could cause data loss or inconsistency after a crash, including starting a checkpoint while creating a multixact or while aborting a prepared transaction. This release also writes the state files of pending prepared transactions atomically, as a crash could previously leave behind an invalid file that prevented the server from starting.
Several fixes to the planner that could produce wrong query results, including queries with LATERAL references, outer joins, self-join elimination on tables using inheritance, DISTINCT ON in a subquery with set-returning functions, and queries using non-deterministic collations.
Several fixes to partition pruning that could cause rows to be missed, including multi-column RANGE-partitioned tables when a query filters only on the leading columns, DEFAULT partitions on tables using MINVALUE or MAXVALUE bounds, and concurrent updates that could silently skip rows that should be updated.
Fix INSERT ... ON CONFLICT to acquire a predicate lock on the conflicting row under SERIALIZABLE isolation. Previously, concurrent updates that should have failed with a serialization error could succeed.
Fix MERGE with WHEN NOT MATCHED BY SOURCE when the target row is concurrently deleted. Previously, a WHEN NOT MATCHED BY TARGET action could run instead, giving incorrect results.
Several fixes for SQL/JSON functions such as JSON_TABLE and JSON_VALUE that could return incorrect results.
Several fixes for logical replication that could cause a subscriber to apply changes incorrectly.
Several fixes for standby servers, including avoiding unnecessary replay delays and query cancellations in certain cases.
Fix psql to accept multiple COPY ... FROM STDIN commands in a single command string. The fix for CVE-2026-6464 caused psql to reject these.
Several fixes that could cause a dump to fail to restore, or cause a restored view to behave differently from the original. These include views and rules that use AT TIME ZONE in a FROM clause or a target alias named set, tsvector and tsquery values that could fail to reload.
Fix the server becoming stuck, instead of exiting, if the startup process crashes while the server is restarting after a crash.

Revision 1.6: download - view: text, markup, annotated - select for diffs
Fri Aug 14 11:42:04 2026 UTC (3 months ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2026Q3-base, pkgsrc-2026Q3
Diff to: previous 1.5: preferred, colored
Changes since revision 1.5: +4 -4 lines
postgresql: updated to 18.6, 17.11, 16.15, 15.19, 14.24

PostgreSQL 18.6, 17.11, 16.15, 15.19, 14.24

Security Issues

The following security vulnerabilities are closed across in this update release. You can find more details about the vulnerabilities and their affected versions in the links below:

CVE-2026-6464: psql COPY FROM STDIN early failure processes data lines as psql commands (CVSS v3.1: 8.1)
CVE-2026-6469: ALTER TABLE ALTER TYPE resets extended statistics ownership (CVSS v3.1: 3.8)
CVE-2026-6470: Fails to check type USAGE privilege (CVSS v3.1: 4.3)
CVE-2026-6471: Logical decoding can dlopen arbitrary file (CVSS v3.1: 7.2)
CVE-2026-14662: tsvector and tsquery undersize allocations, via integer wraparound (CVSS v3.1: 8.8)
CVE-2026-14663: pgcrypto, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext (CVSS v3.1: 6.5)
CVE-2026-14664: Regexp heap buffer overflow executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-14666: Row security caching disregards role modifications (CVSS v3.1: 4.2)
CVE-2026-14668: ctid type confusion in selectivity estimator discloses derivative of arbitrary read (CVSS v3.1: 8.1)
CVE-2026-14669: to_char heap buffer overflow executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-14670: plperl tied object heap buffer overflow executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-14671: refint plan cache type confusion executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-14672: Observable response discrepancy with non-default scram_iterations provides user existence oracle (CVSS v3.1: 5.3)
CVE-2026-14673: amcheck does not clear untrusted search path (CVSS v3.1: 3.8)
CVE-2026-14676: pg_stat_statements heap buffer overflow executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-14677: 32-bit pltcl and plperl undersize allocations, via integer wraparound (CVSS v3.1: 8.8)
CVE-2026-14678: pg_trgm picksplit reads past end of buffer (CVSS v3.1: 4.3)
CVE-2026-14679: Stack buffer overflow in argument match writes 0x0 and 0x1 to server memory (CVSS v3.1: 8.2)
CVE-2026-14680: Type confusion via "internal" arguments (CVSS v3.1: 8.8)
CVE-2026-14681: Improper enforcement of GSSAPI encryption when coupled with SSL (CVSS v3.1: 4.2)
CVE-2026-15741: Expression deparse allows SQL injection via EXTRACT argument (CVSS v3.1: 8.8)
CVE-2026-15742: fuzzystrmatch writes effectively-arbitrary addresses, via integer wraparound (CVSS v3.1: 8.8)
CVE-2026-16238: Type confusion in pg_restore_attribute_stats() executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-16239: Type confusion in cursor CLOSE + DECLARE executes arbitrary code (CVSS v3.1: 8.8)
CVE-2026-16241: ECPG integer underflow can crash the client (CVSS v3.1: 3.8)
CVE-2026-18024: ascii() function reads past end of buffer (CVSS v3.1: 4.3)
CVE-2026-18408: psql \unrestrict lets superuser of pg_dump origin server execute arbitrary code in psql client (CVSS v3.1: 8.8)
CVE-2026-19385: pg_dump heap buffer overflow executes arbitrary code (CVSS v3.1: 8.8)

Bug Fixes and Improvements

Revision 1.4.2.1: download - view: text, markup, annotated - select for diffs
Mon May 18 09:47:03 2026 UTC (5 months, 4 weeks ago) by bsiegert
Branches: pkgsrc-2026Q1
Diff to: previous 1.4: preferred, colored; next MAIN 1.5: preferred, colored
Changes since revision 1.4: +4 -4 lines
Pullup ticket #7117 - requested by taca
databases/postgresql{14,15,16,17,18}: security fix

Revisions pulled up:
- databases/postgresql14-docs/PLIST                             1.24
- databases/postgresql14/Makefile.common                        1.30
- databases/postgresql14/distinfo                               1.26
- databases/postgresql15-docs/PLIST                             1.19
- databases/postgresql15/Makefile.common                        1.24
- databases/postgresql15/distinfo                               1.19
- databases/postgresql16-docs/PLIST                             1.15
- databases/postgresql16/Makefile.common                        1.22
- databases/postgresql16/distinfo                               1.16
- databases/postgresql17-docs/PLIST                             1.11
- databases/postgresql17/Makefile.common                        1.18
- databases/postgresql17/distinfo                               1.11
- databases/postgresql18-docs/PLIST                             1.5
- databases/postgresql18/Makefile.common                        1.6
- databases/postgresql18/distinfo                               1.5

---
   Module Name:	pkgsrc
   Committed By:	adam
   Date:		Fri May 15 08:34:13 UTC 2026

   Modified Files:
   	pkgsrc/databases/postgresql14: Makefile.common distinfo
   	pkgsrc/databases/postgresql14-docs: PLIST
   	pkgsrc/databases/postgresql15: Makefile.common distinfo
   	pkgsrc/databases/postgresql15-docs: PLIST
   	pkgsrc/databases/postgresql16: Makefile.common distinfo
   	pkgsrc/databases/postgresql16-docs: PLIST
   	pkgsrc/databases/postgresql17: Makefile.common distinfo
   	pkgsrc/databases/postgresql17-docs: PLIST
   	pkgsrc/databases/postgresql18: Makefile.common distinfo
   	pkgsrc/databases/postgresql18-docs: PLIST

   Log Message:
   postgresql1*: updated to 18.4, 17.10, 16.14, 15.18, 14.23

   PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23

   This release fixes 11 security vulnerabilities and over 60 bugs reported over the last several months.

   Security Issues

   CVE-2026-6472: PostgreSQL CREATE TYPE does not check multirange schema CREATE privilege

   CVSS v3.1 Base Score: 5.4

   Supported, Vulnerable Versions: 14 - 18.

   Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to find user-defined types, including extension-defined types. That is to say, the victim will execute arbitrary SQL functions of the attacker's choice. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

   The PostgreSQL project thanks Jelte Fennema-Nio for reporting this problem.

   CVE-2026-6473: PostgreSQL server undersizes allocations, via integer wraparound

   CVSS v3.1 Base Score: 8.8

   Supported, Vulnerable Versions: 14 - 18.

   Integer wraparound in multiple PostgreSQL server features allows an application input provider to cause the server to undersize an allocation and write out-of-bounds. This results in a segmentation fault. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

   The PostgreSQL project thanks Anemone, A1ex, Xint Code, Jihe Wang, Jingzhou Fu, Pavel Kohout, Petr Simecek, www.aisle.com, Bruce Dang of Calif.io, and Sven Klemm for reporting this problem.

   CVE-2026-6474: PostgreSQL timeofday() can disclose portions of server memory

   CVSS v3.1 Base Score: 4.3

   Supported, Vulnerable Versions: 14 - 18.

   Externally-controlled format string in PostgreSQL timeofday() function allows an attacker to retrieve portions of server memory, via crafted timezone zones. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

   The PostgreSQL project thanks Xint Code for reporting this problem.

   CVE-2026-6475: PostgreSQL pg_basebackup and pg_rewind can overwrite unrelated files of origin superuser choice

   CVSS v3.1 Base Score: 8.8

   Supported, Vulnerable Versions: 14 - 18.

   Symlink following in PostgreSQL pg_basebackup plain format and in pg_rewind allows an origin superuser to overwrite local files, e.g. /var/lib/postgres/.bashrc, that hijack the operating system account. It will remain the case that starting the server after these commands implicitly trusts the origin superuser, due to features like shared_preload_libraries. Hence, the attack has practical implications only if one takes relevant action between these commands and server start, like moving the files to a different VM or snapshotting the VM. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

   The PostgreSQL project thanks Valery Gubanov, XlabAI Team of Tencent Xuanwu Lab, Atuin Automated Vulnerability Discovery Engine, Zhanpeng Liu (pkugenuine(at)gmail(dot)com), Guannan Wang (wgnbuaa(at)gmail(dot)com), and Guancheng Li (lgcpku(at)gmail(dot)com) for reporting this problem.

   CVE-2026-6476: PostgreSQL pg_createsubscriber allows SQL injection via subscription name

   CVSS v3.1 Base Score: 7.2

   Supported, Vulnerable Versions: 17 - 18.

   SQL injection in PostgreSQL pg_createsubscriber allows an attacker with pg_create_subscription rights to execute arbitrary SQL as a superuser. The attack takes effect when pg_createsubscriber next runs. Within major versions 17 and 18, minor versions before PostgreSQL 18.4 and 17.10 are affected. Versions before PostgreSQL 17 are unaffected.

   The PostgreSQL project thanks Yu Kunpeng for reporting this problem.

   CVE-2026-6477: PostgreSQL libpq lo_* functions let server superuser overwrite client stack memory

   CVSS v3.1 Base Score: 8.8

   Supported, Vulnerable Versions: 14 - 18.

   Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lseek64(), and lo_tell64() functions allows the server superuser to overwrite a client stack buffer with an arbitrarily-large response. Like gets(), PQfn(..., result_is_int=0, ...) stores arbitrary-length, server-determined data into a buffer of unspecified size. Because both the \lo_export command in psql and pg_dump call lo_read(), the server superuser can overwrite pg_dump or psql stack memory. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

   The PostgreSQL project thanks Yu Kunpeng and Martin Heistermann for reporting this problem.

   CVE-2026-6478: PostgreSQL discloses MD5-hashed passwords via covert timing channel

   CVSS v3.1 Base Score: 6.5

   Supported, Vulnerable Versions: 14 - 18.

   Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover user credentials sufficient to authenticate. This does not affect scram-sha-256 passwords, the default in all supported releases. However, current databases may have MD5-hashed passwords originating in upgrades from PostgreSQL 13 or earlier. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

   The PostgreSQL project thanks Joe Conway for reporting this problem.

   CVE-2026-6479: PostgreSQL SSL/GSS init causes denial of service, via uncontrolled recursion

   CVSS v3.1 Base Score: 7.5

   Supported, Vulnerable Versions: 14 - 18.

   Uncontrolled recursion in PostgreSQL SSL and GSS negotiation allows an attacker able to connect to a PostgreSQL AF_UNIX socket to achieve sustained denial of service. If SSL and GSS are both disabled, an attacker can do the same via access to a PostgreSQL TCP socket. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

   The PostgreSQL project thanks Calif.io in collaboration with Claude and Anthropic Research for reporting this problem.

   CVE-2026-6575: PostgreSQL pg_restore_attribute_stats accepts values that cause query planning to read past end of stats array

   CVSS v3.1 Base Score: 4.3

   Supported, Vulnerable Versions: 18.

   Buffer over-read in PostgreSQL function pg_restore_attribute_stats() accepts array values of unmatched length, which causes query planning to read past end of one array. This allows a table maintainer to infer memory values past that array end. Within major version 18, minor versions before PostgreSQL 18.4 are affected. Versions before PostgreSQL 18 are unaffected.

   The PostgreSQL project thanks Jeroen Gui for reporting this problem.

   CVE-2026-6637: PostgreSQL refint allows stack buffer overflow and SQL injection

   CVSS v3.1 Base Score: 8.8

   Supported, Vulnerable Versions: 14 - 18.

   Stack buffer overflow in PostgreSQL module refint allows an unprivileged database user to execute arbitrary code as the operating system user running the database. A distinct attack is possible if the application declares a user-controlled column as a refint cascade primary key and facilitates user-controlled updates to that column. In that case, a SQL injection allows a primary key update value provider to execute arbitrary SQL as the database user performing the primary key update. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

   The PostgreSQL project thanks Nikolay Samokhvalov for reporting this problem.

   CVE-2026-6638: PostgreSQL REFRESH PUBLICATION allows SQL injection via table name

   CVSS v3.1 Base Score: 3.7

   Supported, Vulnerable Versions: 16 - 18.

   SQL injection in PostgreSQL logical replication ALTER SUBSCRIPTION ... REFRESH PUBLICATION allows a subscriber table creator to execute arbitrary SQL with the subscription's publication-side credentials. The attack takes effect at the next REFRESH PUBLICATION. Within major versions 16, 17, and 18, minor versions before PostgreSQL 18.4, 17.10, and 16.14 are affected. Versions before PostgreSQL 16 are unaffected.

   The PostgreSQL project thanks Pavel Kohout, Aisle Research for reporting this problem.

   Bug Fixes and Improvements

   This update fixes over 60 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 18. Some of these issues may also affect other supported versions of PostgreSQL.

   Fix queries that could return incorrect results when using a nondeterministic collation over a unique index.
   Fix loss of deferrability of foreign-key triggers. Previously, a foreign key defined as DEFERRABLE INITIALLY DEFERRED would behave as NOT DEFERRABLE after being set to NOT ENFORCED status and then back to ENFORCED. If you have a foreign key with this problem, after installing this update you can fix it by setting it to NOT ENFORCED and then back to ENFORCED.
   Improve the planner's ability to apply partition pruning to more cases.
   Fix self-join removal to handle join clauses that are only boolean columns, for example, ON t1.boolcol.
   Several fixes around virtual generated columns, including ensuring INSERT ... ON CONFLICT works when EXCLUDED references a virtual generated column.
   Report a serialization failure when MERGE encounters a concurrently-updated tuple in "repeatable read" or "serializable" isolation modes.
   Fix CREATE TABLE ... LIKE ... INCLUDING STATISTICS for cases where the source table had one or more dropped columns.
   Fix WITHOUT OVERLAPS to allow domains.
   Disallow making a composite type be a member of itself via a multirange.
   Fix sometimes-incorrect results when array_agg(anyarray) executes in parallel.
   Prevent bloating during restore of an incremental backup.
   Prevent stuck logical replication slot synchronization worker processes from blocking promotion of a standby server.
   Make the pg_aios system view pid column show NULL instead of 0 when an entry has no owning process.
   Fix cases where pg_stat_replication shows NULL lag even while replication is active.
   Correctly display JOIN alias variables that are used in GROUP BY.
   If the startup process fails, properly shut down other child processes before exiting the postmaster.
   Fix race condition that could cause a standby server following WAL from a primary of an older minor version to get into a crash-and-restart loop.
   Prevent indefinite wait in shutdown of a walsender process when logical replication is actively publishing data.
   Ensure that free space map changes are persisted during recovery. This could have performance ramifications on a standby server after promotion.
   Fix assorted bugs in backup decompression and tar-parsing code used in pg_basebackup and pg_verifybackup.
   Ensure pg_dumpall doesn't skip role grants with dangling grantor OIDs, restoring the behavior before PostgreSQL 16. Emits a warning about missing grantor if the source server is PostgreSQL 16 or later.
   Fix pg_upgrade to use the correct protocol version when connecting to older source servers.
   Fix output in pg_overexplain when using the RANGE_TABLE option.
   Fix postgres_fdw crash due to premature cleanup of a failed connection.

Revision 1.5: download - view: text, markup, annotated - select for diffs
Fri May 15 08:34:12 2026 UTC (6 months ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2026Q2-base, pkgsrc-2026Q2
Diff to: previous 1.4: preferred, colored
Changes since revision 1.4: +4 -4 lines
postgresql1*: updated to 18.4, 17.10, 16.14, 15.18, 14.23

PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23

This release fixes 11 security vulnerabilities and over 60 bugs reported over the last several months.

Security Issues

CVE-2026-6472: PostgreSQL CREATE TYPE does not check multirange schema CREATE privilege

CVSS v3.1 Base Score: 5.4

Supported, Vulnerable Versions: 14 - 18.

Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to find user-defined types, including extension-defined types. That is to say, the victim will execute arbitrary SQL functions of the attacker's choice. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

The PostgreSQL project thanks Jelte Fennema-Nio for reporting this problem.

CVE-2026-6473: PostgreSQL server undersizes allocations, via integer wraparound

CVSS v3.1 Base Score: 8.8

Supported, Vulnerable Versions: 14 - 18.

Integer wraparound in multiple PostgreSQL server features allows an application input provider to cause the server to undersize an allocation and write out-of-bounds. This results in a segmentation fault. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

The PostgreSQL project thanks Anemone, A1ex, Xint Code, Jihe Wang, Jingzhou Fu, Pavel Kohout, Petr Simecek, www.aisle.com, Bruce Dang of Calif.io, and Sven Klemm for reporting this problem.

CVE-2026-6474: PostgreSQL timeofday() can disclose portions of server memory

CVSS v3.1 Base Score: 4.3

Supported, Vulnerable Versions: 14 - 18.

Externally-controlled format string in PostgreSQL timeofday() function allows an attacker to retrieve portions of server memory, via crafted timezone zones. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

The PostgreSQL project thanks Xint Code for reporting this problem.

CVE-2026-6475: PostgreSQL pg_basebackup and pg_rewind can overwrite unrelated files of origin superuser choice

CVSS v3.1 Base Score: 8.8

Supported, Vulnerable Versions: 14 - 18.

Symlink following in PostgreSQL pg_basebackup plain format and in pg_rewind allows an origin superuser to overwrite local files, e.g. /var/lib/postgres/.bashrc, that hijack the operating system account. It will remain the case that starting the server after these commands implicitly trusts the origin superuser, due to features like shared_preload_libraries. Hence, the attack has practical implications only if one takes relevant action between these commands and server start, like moving the files to a different VM or snapshotting the VM. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

The PostgreSQL project thanks Valery Gubanov, XlabAI Team of Tencent Xuanwu Lab, Atuin Automated Vulnerability Discovery Engine, Zhanpeng Liu (pkugenuine(at)gmail(dot)com), Guannan Wang (wgnbuaa(at)gmail(dot)com), and Guancheng Li (lgcpku(at)gmail(dot)com) for reporting this problem.

CVE-2026-6476: PostgreSQL pg_createsubscriber allows SQL injection via subscription name

CVSS v3.1 Base Score: 7.2

Supported, Vulnerable Versions: 17 - 18.

SQL injection in PostgreSQL pg_createsubscriber allows an attacker with pg_create_subscription rights to execute arbitrary SQL as a superuser. The attack takes effect when pg_createsubscriber next runs. Within major versions 17 and 18, minor versions before PostgreSQL 18.4 and 17.10 are affected. Versions before PostgreSQL 17 are unaffected.

The PostgreSQL project thanks Yu Kunpeng for reporting this problem.

CVE-2026-6477: PostgreSQL libpq lo_* functions let server superuser overwrite client stack memory

CVSS v3.1 Base Score: 8.8

Supported, Vulnerable Versions: 14 - 18.

Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lseek64(), and lo_tell64() functions allows the server superuser to overwrite a client stack buffer with an arbitrarily-large response. Like gets(), PQfn(..., result_is_int=0, ...) stores arbitrary-length, server-determined data into a buffer of unspecified size. Because both the \lo_export command in psql and pg_dump call lo_read(), the server superuser can overwrite pg_dump or psql stack memory. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

The PostgreSQL project thanks Yu Kunpeng and Martin Heistermann for reporting this problem.

CVE-2026-6478: PostgreSQL discloses MD5-hashed passwords via covert timing channel

CVSS v3.1 Base Score: 6.5

Supported, Vulnerable Versions: 14 - 18.

Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover user credentials sufficient to authenticate. This does not affect scram-sha-256 passwords, the default in all supported releases. However, current databases may have MD5-hashed passwords originating in upgrades from PostgreSQL 13 or earlier. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

The PostgreSQL project thanks Joe Conway for reporting this problem.

CVE-2026-6479: PostgreSQL SSL/GSS init causes denial of service, via uncontrolled recursion

CVSS v3.1 Base Score: 7.5

Supported, Vulnerable Versions: 14 - 18.

Uncontrolled recursion in PostgreSQL SSL and GSS negotiation allows an attacker able to connect to a PostgreSQL AF_UNIX socket to achieve sustained denial of service. If SSL and GSS are both disabled, an attacker can do the same via access to a PostgreSQL TCP socket. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

The PostgreSQL project thanks Calif.io in collaboration with Claude and Anthropic Research for reporting this problem.

CVE-2026-6575: PostgreSQL pg_restore_attribute_stats accepts values that cause query planning to read past end of stats array

CVSS v3.1 Base Score: 4.3

Supported, Vulnerable Versions: 18.

Buffer over-read in PostgreSQL function pg_restore_attribute_stats() accepts array values of unmatched length, which causes query planning to read past end of one array. This allows a table maintainer to infer memory values past that array end. Within major version 18, minor versions before PostgreSQL 18.4 are affected. Versions before PostgreSQL 18 are unaffected.

The PostgreSQL project thanks Jeroen Gui for reporting this problem.

CVE-2026-6637: PostgreSQL refint allows stack buffer overflow and SQL injection

CVSS v3.1 Base Score: 8.8

Supported, Vulnerable Versions: 14 - 18.

Stack buffer overflow in PostgreSQL module refint allows an unprivileged database user to execute arbitrary code as the operating system user running the database. A distinct attack is possible if the application declares a user-controlled column as a refint cascade primary key and facilitates user-controlled updates to that column. In that case, a SQL injection allows a primary key update value provider to execute arbitrary SQL as the database user performing the primary key update. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

The PostgreSQL project thanks Nikolay Samokhvalov for reporting this problem.

CVE-2026-6638: PostgreSQL REFRESH PUBLICATION allows SQL injection via table name

CVSS v3.1 Base Score: 3.7

Supported, Vulnerable Versions: 16 - 18.

SQL injection in PostgreSQL logical replication ALTER SUBSCRIPTION ... REFRESH PUBLICATION allows a subscriber table creator to execute arbitrary SQL with the subscription's publication-side credentials. The attack takes effect at the next REFRESH PUBLICATION. Within major versions 16, 17, and 18, minor versions before PostgreSQL 18.4, 17.10, and 16.14 are affected. Versions before PostgreSQL 16 are unaffected.

The PostgreSQL project thanks Pavel Kohout, Aisle Research for reporting this problem.

Bug Fixes and Improvements

This update fixes over 60 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 18. Some of these issues may also affect other supported versions of PostgreSQL.

Fix queries that could return incorrect results when using a nondeterministic collation over a unique index.
Fix loss of deferrability of foreign-key triggers. Previously, a foreign key defined as DEFERRABLE INITIALLY DEFERRED would behave as NOT DEFERRABLE after being set to NOT ENFORCED status and then back to ENFORCED. If you have a foreign key with this problem, after installing this update you can fix it by setting it to NOT ENFORCED and then back to ENFORCED.
Improve the planner's ability to apply partition pruning to more cases.
Fix self-join removal to handle join clauses that are only boolean columns, for example, ON t1.boolcol.
Several fixes around virtual generated columns, including ensuring INSERT ... ON CONFLICT works when EXCLUDED references a virtual generated column.
Report a serialization failure when MERGE encounters a concurrently-updated tuple in "repeatable read" or "serializable" isolation modes.
Fix CREATE TABLE ... LIKE ... INCLUDING STATISTICS for cases where the source table had one or more dropped columns.
Fix WITHOUT OVERLAPS to allow domains.
Disallow making a composite type be a member of itself via a multirange.
Fix sometimes-incorrect results when array_agg(anyarray) executes in parallel.
Prevent bloating during restore of an incremental backup.
Prevent stuck logical replication slot synchronization worker processes from blocking promotion of a standby server.
Make the pg_aios system view pid column show NULL instead of 0 when an entry has no owning process.
Fix cases where pg_stat_replication shows NULL lag even while replication is active.
Correctly display JOIN alias variables that are used in GROUP BY.
If the startup process fails, properly shut down other child processes before exiting the postmaster.
Fix race condition that could cause a standby server following WAL from a primary of an older minor version to get into a crash-and-restart loop.
Prevent indefinite wait in shutdown of a walsender process when logical replication is actively publishing data.
Ensure that free space map changes are persisted during recovery. This could have performance ramifications on a standby server after promotion.
Fix assorted bugs in backup decompression and tar-parsing code used in pg_basebackup and pg_verifybackup.
Ensure pg_dumpall doesn't skip role grants with dangling grantor OIDs, restoring the behavior before PostgreSQL 16. Emits a warning about missing grantor if the source server is PostgreSQL 16 or later.
Fix pg_upgrade to use the correct protocol version when connecting to older source servers.
Fix output in pg_overexplain when using the RANGE_TABLE option.
Fix postgres_fdw crash due to premature cleanup of a failed connection.

Revision 1.4: download - view: text, markup, annotated - select for diffs
Thu Feb 26 17:18:54 2026 UTC (8 months, 2 weeks ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2026Q1-base
Branch point for: pkgsrc-2026Q1
Diff to: previous 1.3: preferred, colored
Changes since revision 1.3: +4 -4 lines
postgresql1[4-8]: updated to 18.3, 17.9, 16.13, 15.17, 14.22

PostgreSQL 18.3, 17.9, 16.13, 15.17, and 14.22

Bug Fixes and Improvements

This update fixes several bugs that were reported since the previous release. The issues listed below affect PostgreSQL 18. Some of these issues may also affect other supported versions of PostgreSQL.

Fix issue where a standby would halt and return an error "could not access status of transaction".
Fix error where the substring() function would raise an error "invalid byte sequence for encoding" on non-ASCII text values if the source of that value is a database column. This was due to a change introduced for the fix to CVE-2026-2006.
Fix for the strict_word_similarity function in pg_trgm that could lead to incorrect output or crashes. This was due to an oversight in the fix for CVE-2026-2007.
Fix function volatility for json_strip_nulls() and jsonb_strip_nulls() to be immutable, like previous releases, allowing for them to be used in indexes. If you previously upgraded to PostgreSQL 18.0 through 18.2, see the additional steps in the "Updating" section.
Fix for NOT NULL tests in LATERAL UNION ALL subquery that could lead to wrong query output.
Avoid NOT NULL constraints from generating name conflicts with user-written constraints.
Fix pg_stat_get_backend_wait_event() and pg_stat_get_backend_wait_event_type() to report values for auxiliary processes, similar to pg_stat_activity.
Fix casting a composite-type variable to a domain type when returning its value from a PL/pgSQL function.
Fix the hstore binary input function to avoid crashes on input with duplicate keys.

Revision 1.3: download - view: text, markup, annotated - select for diffs
Fri Feb 13 10:52:25 2026 UTC (9 months ago) by adam
Branches: MAIN
Diff to: previous 1.2: preferred, colored
Changes since revision 1.2: +4 -4 lines
postgresql1[4-8]*: updated to 18.2, 17.8, 16.12, 15.16, and 14.21

PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21

Security Issues

CVE-2026-2003: PostgreSQL oidvector discloses a few bytes of memory

CVSS v3.1 Base Score: 4.3

Supported, Vulnerable Versions: 14 - 18.

Improper validation of type oidvector in PostgreSQL allows a database user to disclose a few bytes of server memory. We have not ruled out viability of attacks that arrange for presence of confidential information in disclosed bytes, but they seem unlikely. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

The PostgreSQL project thanks Altan Birler for reporting this problem.

CVE-2026-2004: PostgreSQL intarray missing validation of type of input to selectivity estimator executes arbitrary code

CVSS v3.1 Base Score: 8.8

Supported, Vulnerable Versions: 14 - 18.

Missing validation of type of input in PostgreSQL intarray extension selectivity estimator function allows an object creator to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

The PostgreSQL project thanks Daniel Firer, as part of zeroday.cloud, for reporting this problem.

CVE-2026-2005: PostgreSQL pgcrypto heap buffer overflow executes arbitrary code

CVSS v3.1 Base Score: 8.8

Supported, Vulnerable Versions: 14 - 18.

Heap buffer overflow in PostgreSQL pgcrypto allows a ciphertext provider to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

The PostgreSQL project thanks Team Xint Code, as part of zeroday.cloud, for reporting this problem.

CVE-2026-2006: PostgreSQL missing validation of multibyte character length executes arbitrary code

CVSS v3.1 Base Score: 8.8

Supported, Vulnerable Versions: 14 - 18.

Missing validation of multibyte character length in PostgreSQL text manipulation allows a database user to issue crafted queries that achieve a buffer overrun. That suffices to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

The PostgreSQL project thanks Paul Gerste and Moritz Sanft, as part of zeroday.cloud, for reporting this problem.

CVE-2026-2007: PostgreSQL pg_trgm heap buffer overflow writes pattern onto server memory

CVSS v3.1 Base Score: 8.2

Supported, Vulnerable Versions: 18.

Heap buffer overflow in PostgreSQL pg_trgm allows a database user to achieve unknown impacts via a crafted input string. The attacker has limited control over the byte patterns to be written, but we have not ruled out the viability of attacks that lead to privilege escalation. PostgreSQL 18.1 and 18.0 are affected.

The PostgreSQL project thanks Heikki Linnakangas for reporting this problem.

Bug Fixes and Improvements

This update fixes over 65 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 18. Some of these issues may also affect other supported versions of PostgreSQL.

Fix inconsistent case-insensitive text matching in the ltree extension. If you use an index on an ltree column, in some cases you may need perform a reindex. See the "Updating" section for additional instructions.
Executing ALTER TABLE ... ADD CONSTRAINT to add a NOT NULL constraint on a column that already is marked as NOT NULL now requires the constraint name to match the existing constraint name.
Fix trigger behavior when MERGE is executed from a WITH query to include rows affected by the MERGE.
Several query planner fixes.
Fix for text substring search for non-deterministic collations.
Several fixes for NOTIFY error handling and reporting.
Use the correct ordering function in GIN index parallel builds.
Fix incorrect handling of incremental backups with tables larger than 1GB.
Fail recovery if WAL does not exist back to the redo point indicated by the checkpoint record.
Fix for ALTER PUBLICATION to ensure event triggers contain all set options.
Several fixes around replication slot initialization.
Don't advance replication slot after a logical replication parallel worker apply failure to prevent transaction loss on the subscriber.
Fix error reporting for SQL/JSON path type mismatches.
Fix JIT compilation function inlining when using LLVM 17 or later.
Add new server parameter file_extend_method to control use of posix_fallocate().
Fix psql tab completion for the VACUUM command options.
Fix pg_dump to handle concurrent sequence drops gracefully and to fail if the calling user explicitly lacks privileges to read the sequence.
Several fixes for amcheck around btree inspection.
Avoid crash in pg_stat_statements when an IN list contains both constants and non-constant expressions.
This release also updates time zone data files to tzdata release 2025c, which only has a historical data change for pre-1976 timestamps in Baja California.

Revision 1.2: download - view: text, markup, annotated - select for diffs
Sat Nov 15 06:39:26 2025 UTC (12 months ago) by adam
Branches: MAIN
CVS tags: pkgsrc-2025Q4-base, pkgsrc-2025Q4
Diff to: previous 1.1: preferred, colored
Changes since revision 1.1: +4 -4 lines
postgresql: updated to 18.1, 17.7, 16.11, 15.15, 14.20, 13.23

PostgreSQL 18.1, 17.7, 16.11, 15.15, 14.20, and 13.23

Security Issues
- CVE-2025-12817: PostgreSQL CREATE STATISTICS does not check for schema CREATE privilege
- CVE-2025-12818: PostgreSQL libpq undersizes allocations, via integer wraparound

Bug Fixes and Improvements

This update fixes over 50 bugs that were reported in the last several months. The issues listed below affect PostgreSQL 18. Some of these issues may also affect other supported versions of PostgreSQL.

Avoid returning duplicate rows from hash right semi-joins.
Avoid possible out-of-memory failures during parallel GIN index build.
Several fixes for BRIN indexes.
Fixes for crashes related to partitioned tables, including one occurring during a recheck.
Avoid duplicating hash partition constraints during DETACH CONCURRENTLY, which previously caused issues during dump/restore or if a parent table is dropped after the DETACH.
Disallow generated columns in partition keys and in COPY ... FROM ... WHERE clauses.
Fix incorrect reporting of replication lag in pg_stat_replication view.
Avoid failures when synchronized_standby_slots references nonexistent replication slots.
Avoid unwanted WAL receiver shutdown when switching from streaming to archive WAL source.
Avoid unnecessary invalidation of logical replication slots.
Correctly handle GROUP BY DISTINCT in PL/pgSQL assignment statements.
Avoid leaking memory when handling a SQL error within PL/Python.
Fix how libpq handles socket-related errors on Windows within its GSSAPI logic.
Fix dumping of non-inherited NOT NULL constraints on inherited table columns.
Ensure consistent ordering of foreign key constraints in the output of pg_dump.
Several fixes for pgbench error handling and reporting.
Fix memory leak in pg_combinebackup.
Allow nonsuperusers with SELECT privileges on a table to use pg_prewarm to prewarm indexes on that table.

Revision 1.1: download - view: text, markup, annotated - select for diffs
Mon Oct 6 13:30:22 2025 UTC (13 months, 1 week ago) by adam
Branches: MAIN
postgresql18: added version 18.0

PostgreSQL 18 improves performance for workloads of all sizes through a new I/O
subsystem that has demonstrated up to 3× performance improvements when reading
from storage, and also increases the number of queries that can use indexes.
This release makes major-version upgrades less disruptive, accelerating upgrade
times and reducing the time required to reach expected performance after an
upgrade completes. Developers also benefit from PostgreSQL 18 features,
including virtual generated columns that compute values at query time, and the
database-friendly uuidv7() function that provides better indexing and read
performance for UUIDs. PostgreSQL 18 makes it easier to integrate with
single-sign on (SSO) systems with support for OAuth 2.0 authentication.

Diff request

This form allows you to request diffs between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.

Log view options

CVSweb <webmaster@jp.NetBSD.org>