Format: 1.8 Date: Mon, 11 May 2026 22:49:32 +0200 Source: postgresql-18 Architecture: source Version: 18.4-1 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers Changed-By: Christoph Berg Closes: 1124468 Changes: postgresql-18 (18.4-1) unstable; urgency=medium . [ Christoph Berg ] * New upstream version 18.4. . + Prevent unbounded recursion while processing startup packets (Michael Paquier) . A malicious client could crash the connected backend by alternating rejected SSL and GSS encryption requests indefinitely. . The PostgreSQL Project thanks Calif.io (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-6479) . + Fix assorted integer overflows in memory-allocation calculations (Tom Lane, Nathan Bossart, Heikki Linnakangas) . Various places were incautious about the possibility of integer overflow in calculations of how much memory to allocate. Overflow would lead to allocating a too-small buffer which the caller would then write past the end of. This would at least trigger server crashes, and probably could be exploited for arbitrary code execution. In many but by no means all cases, the hazard exists only in 32-bit builds. . The PostgreSQL Project thanks Xint Code, Bruce Dang, Sven Klemm, and Pavel Kohout for reporting these problems. (CVE-2026-6473) . + Properly quote subscription names in pg_createsubscriber (Nathan Bossart) . The given subscription name was inserted into SQL commands without quoting, so that SQL injection could be achieved in the (perhaps unlikely) case that the subscription name comes from an untrusted source. . The PostgreSQL Project thanks Yu Kunpeng for reporting this problem. (CVE-2026-6476) . + Properly quote object names in logical replication origin checks (Pavel Kohout) . ALTER SUBSCRIPTION ... REFRESH PUBLICATION interpolated schema and relation names into SQL commands without quoting them, allowing execution of arbitrary SQL on the publisher. . The PostgreSQL Project thanks Pavel Kohout for reporting this problem. (CVE-2026-6638) . + Reject over-length options in ts_headline() (Michael Paquier) . The StartSel, StopSel and FragmentDelimiter strings must not exceed 32Kb in length, but this was not checked for. An over-length value would typically crash the server. . The PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6473) . + Detect faulty input when restoring attribute MCV statistics (Michael Paquier) . The statistics restore functions were insufficiently careful about validating most-common-value statistics, and would accept values that could crash the planner later on. . The PostgreSQL Project thanks Jeroen Gui for reporting this problem. (CVE-2026-6575) . + Guard against malicious time zone names in timeofday() and pg_strftime() (Tom Lane) . A crafted time zone setting could pass % sequences to snprintf(), potentially causing crashes or disclosure of server memory. Another path to similar results was to overflow the limited-size output buffer used by pg_strftime(). . The PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6474) . + When creating a multirange type, ensure the user has CREATE privilege on the schema specified for the multirange type (Jelte Fennema-Nio) . The multirange type can be put into a different schema than its parent range type, but we neglected to apply the required privilege check when doing so. . The PostgreSQL Project thanks Jelte Fennema-Nio for reporting this problem. (CVE-2026-6472) . + Use timing-safe string comparisons in authentication code (Michael Paquier) . Use timingsafe_bcmp() instead of memcpy() or strcmp() when checking passwords, hashes, etc. It is not known whether the data dependency of those functions is usefully exploitable in any of these places, but in the interests of safety, replace them. . The PostgreSQL Project thanks Joe Conway for reporting this problem. (CVE-2026-6478) . + Mark PQfn() as unsafe, and avoid using it within libpq (Nathan Bossart) . For a non-integral result type, PQfn() is not passed the size of the output buffer, so it cannot check that the data returned by the server will fit. A malicious server could therefore overwrite client memory. This is unfixable without an API change, so mark the function as deprecated. Internally to libpq, use a variant version that can apply the missing check. . The PostgreSQL Project thanks Yu Kunpeng and Martin Heistermann for reporting this problem. (CVE-2026-6477) . + Prevent path traversal in pg_basebackup and pg_rewind (Michael Paquier) . These applications failed to validate output file paths read from their input, so that a malicious source could overwrite any file writable by these applications. Constrain where data can be written by rejecting paths that are absolute or contain parent-directory references. . The PostgreSQL Project thanks XlabAI Team of Tencent Xuanwu Lab and Valery Gubanov for reporting this problem. (CVE-2026-6475) . + Guard against field overflow within contrib/intarray's query_int type and contrib/ltree's ltxtquery type (Tom Lane) . Parsing of these query structures did not check for overflow of 16-bit fields, so that construction of an invalid query tree was possible. This can crash the server when executing the query. . The PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6473) . + Guard against overly long values of contrib/ltree's lquery type (Michael Paquier) . Values with more than 64K items caused internal overflows, potentially resulting in stack smashes or wrong answers. . The PostgreSQL Project thanks Vergissmeinnicht, A1ex, and Jihe Wang for reporting this problem. (CVE-2026-6473) . + Prevent SQL injection and buffer overruns in contrib/spi (Nathan Bossart) . check_foreign_key() was insufficiently careful about quoting key values, and also used fixed-length buffers for constructing queries. While this module is only meant as example code, it still shouldn't contain such dangerous errors. . The PostgreSQL Project thanks Nikolay Samokhvalov for reporting this problem. (CVE-2026-6637) . * Add zh_TW, zh_CN debconf translations. Thanks Yangfl! (Closes: #1124468) . [ Michael Banck ] * Add patch that fixes TAP tests on hurd. Checksums-Sha1: 3cb5ce320f0a528de4dcee5b610bf7706218b5f4 4752 postgresql-18_18.4-1.dsc 25d1499917475db9f3129a7f658b7b005b577da8 22567173 postgresql-18_18.4.orig.tar.bz2 4b5bf58abd2ce26266498df9b05d9baa8365eaa0 27900 postgresql-18_18.4-1.debian.tar.xz Checksums-Sha256: 149b0158c6689dbb4fc924e5d80375f4a8595e0eea4fb512dc6aea397f220475 4752 postgresql-18_18.4-1.dsc 81a81ec695fb0c7901407defaa1d2f7973617154cf27ba74e3a7ab8e64436094 22567173 postgresql-18_18.4.orig.tar.bz2 1144b0f797277955a5b09c6bef1ff4030f2a9c7bf6285af53e7a2af78c193a73 27900 postgresql-18_18.4-1.debian.tar.xz Files: 61fb00cf5dc05ed8bb67269cdc333c0d 4752 database optional postgresql-18_18.4-1.dsc f985597ebb8e71f338beb2bef974b6ed 22567173 database optional postgresql-18_18.4.orig.tar.bz2 3ef451c68c131b9c8512be36c56fe613 27900 database optional postgresql-18_18.4-1.debian.tar.xz Location: DEFERRED Delayed-Until: 2026-05-14 13:01:58 Delay-Remaining: 1 days 21:05 Fingerprint: 5C48FE6157F49179597087C64C5A6BAB12D2A7AE