It was discovered that PostgreSQL incorrectly handled COPY FROM STDIN when an early failure occurred. An authenticated user could possibly use this issue to execute arbitrary SQL commands. ( CVE-2026-6464 ) It was discovered that PostgreSQL incorrectly reset extended statistics ownership during ALTER TABLE ALTER TYPE operations. An attacker could possibly use this issue to obtain sensitive information or gain unintended privileges. ( CVE-2026-6469 ) It was discovered that PostgreSQL failed to check the USAGE privilege on types. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-6470 ) It was discovered that PostgreSQL logical decoding could load arbitrary shared libraries. An authenticated user could possibly use this issue to execute arbitrary code. (
It was discovered that PostgreSQL incorrectly handled COPY FROM STDIN when an early failure occurred. An authenticated user could possibly use this issue to execute arbitrary SQL commands. ( CVE-2026-6464 )
It was discovered that PostgreSQL incorrectly reset extended statistics ownership during ALTER TABLE ALTER TYPE operations. An attacker could possibly use this issue to obtain sensitive information or gain unintended privileges. ( CVE-2026-6469 )
It was discovered that PostgreSQL failed to check the USAGE privilege on types. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-6470 )
It was discovered that PostgreSQL logical decoding could load arbitrary shared libraries. An authenticated user could possibly use this issue to execute arbitrary code. (
It was discovered that PostgreSQL incorrectly handled COPY FROM STDIN when an early failure occurred. An authenticated user could possibly use this issue to execute arbitrary SQL commands. ( CVE-2026-6464 ) It was discovered that PostgreSQL incorrectly reset extended statistics ownership during ALTER TABLE ALTER TYPE operations. An attacker could possibly use this issue to obtain sensitive information or gain unintended privileges. ( CVE-2026-6469 ) It was discovered that PostgreSQL failed to check the USAGE privilege on types. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-6470 ) It was discovered that PostgreSQL logical decoding could load arbitrary shared libraries. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-6471 ) It was discovered that PostgreSQL had integer wraparound issues in tsvector and tsquery allocations. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14662 ) It was discovered that PostgreSQL pgcrypto silently used cleartext when OpenSSL-disabled ciphers were requested. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-14663 ) It was discovered that PostgreSQL had a heap buffer overflow in regular expression processing. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14664 ) It was discovered that PostgreSQL row security policies were not properly invalidated when roles were modified. An attacker could possibly use this issue to bypass intended row security restrictions. ( CVE-2026-14666 ) It was discovered that PostgreSQL had a type confusion issue in the selectivity estimator involving ctid. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-14668 ) It was discovered that PostgreSQL had a heap buffer overflow in the to_char function. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14669 ) It was discovered that PostgreSQL had a heap buffer overflow in the PL/Perl tied object handling. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14670 ) It was discovered that PostgreSQL had a type confusion issue in the referential integrity plan cache. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14671 ) It was discovered that PostgreSQL had an observable response discrepancy when non-default scram_iterations were used. A remote attacker could possibly use this issue to enumerate valid usernames. This issue only affected Ubuntu 24.04 LTS and Ubuntu 26.04 LTS. ( CVE-2026-14672 ) It was discovered that PostgreSQL amcheck did not clear untrusted paths. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14673 ) It was discovered that PostgreSQL had a heap buffer overflow in pg_stat_statements. An authenticated user could possibly use this issue to execute arbitrary code. This issue only affected Ubuntu 26.04 LTS. ( CVE-2026-14676 ) It was discovered that PostgreSQL had integer wraparound issues in PL/Tcl and PL/Perl allocations on 32-bit systems. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14677 ) It was discovered that PostgreSQL pg_trgm read past the end of a buffer during picksplit operations. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-14678 ) It was discovered that PostgreSQL had a stack buffer overflow in argument matching. An authenticated user could possibly use this issue to corrupt server memory. ( CVE-2026-14679 ) It was discovered that PostgreSQL had a type confusion issue when functions used internal arguments. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14680 ) It was discovered that PostgreSQL did not properly enforce GSSAPI encryption when used together with SSL. An attacker could possibly use this issue to perform a machine-in-the-middle attack and obtain sensitive information. This issue only affected Ubuntu 26.04 LTS. ( CVE-2026-14681 ) It was discovered that PostgreSQL allowed SQL injection through EXTRACT arguments during expression deparsing. An authenticated user could possibly use this issue to perform SQL injection attacks. ( CVE-2026-15741 ) It was discovered that PostgreSQL fuzzystrmatch had integer wraparound issues that could write to arbitrary addresses. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-15742 ) It was discovered that PostgreSQL had a type confusion issue in pg_restore_attribute_stats(). An authenticated user could possibly use this issue to execute arbitrary code. This issue only affected Ubuntu 26.04 LTS. ( CVE-2026-16238 ) It was discovered that PostgreSQL had a type confusion issue when handling cursor CLOSE and DECLARE operations. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-16239 ) It was discovered that PostgreSQL had an integer underflow in the ECPG client library. An attacker could possibly use this issue to cause PostgreSQL to crash, resulting in a denial of service. ( CVE-2026-16241 ) It was discovered that PostgreSQL had an out-of-bounds read in the ascii() function. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-18024 ) It was discovered that the psql \unrestrict command allowed the superuser of a pg_dump origin server to execute arbitrary code in the psql client. An attacker could possibly use this issue to execute arbitrary code. ( CVE-2026-18408 ) It was discovered that PostgreSQL pg_dump had a heap buffer overflow. An attacker could possibly use this issue to execute arbitrary code. ( CVE-2026-19385 )
It was discovered that PostgreSQL incorrectly handled COPY FROM STDIN when an early failure occurred. An authenticated user could possibly use this issue to execute arbitrary SQL commands. ( CVE-2026-6464 )
It was discovered that PostgreSQL incorrectly reset extended statistics ownership during ALTER TABLE ALTER TYPE operations. An attacker could possibly use this issue to obtain sensitive information or gain unintended privileges. ( CVE-2026-6469 )
It was discovered that PostgreSQL failed to check the USAGE privilege on types. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-6470 )
It was discovered that PostgreSQL logical decoding could load arbitrary shared libraries. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-6471 )
It was discovered that PostgreSQL had integer wraparound issues in tsvector and tsquery allocations. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14662 )
It was discovered that PostgreSQL pgcrypto silently used cleartext when OpenSSL-disabled ciphers were requested. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-14663 )
It was discovered that PostgreSQL had a heap buffer overflow in regular expression processing. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14664 )
It was discovered that PostgreSQL row security policies were not properly invalidated when roles were modified. An attacker could possibly use this issue to bypass intended row security restrictions. ( CVE-2026-14666 )
It was discovered that PostgreSQL had a type confusion issue in the selectivity estimator involving ctid. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-14668 )
It was discovered that PostgreSQL had a heap buffer overflow in the to_char function. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14669 )
It was discovered that PostgreSQL had a heap buffer overflow in the PL/Perl tied object handling. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14670 )
It was discovered that PostgreSQL had a type confusion issue in the referential integrity plan cache. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14671 )
It was discovered that PostgreSQL had an observable response discrepancy when non-default scram_iterations were used. A remote attacker could possibly use this issue to enumerate valid usernames. This issue only affected Ubuntu 24.04 LTS and Ubuntu 26.04 LTS. ( CVE-2026-14672 )
It was discovered that PostgreSQL amcheck did not clear untrusted paths. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14673 )
It was discovered that PostgreSQL had a heap buffer overflow in pg_stat_statements. An authenticated user could possibly use this issue to execute arbitrary code. This issue only affected Ubuntu 26.04 LTS. ( CVE-2026-14676 )
It was discovered that PostgreSQL had integer wraparound issues in PL/Tcl and PL/Perl allocations on 32-bit systems. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14677 )
It was discovered that PostgreSQL pg_trgm read past the end of a buffer during picksplit operations. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-14678 )
It was discovered that PostgreSQL had a stack buffer overflow in argument matching. An authenticated user could possibly use this issue to corrupt server memory. ( CVE-2026-14679 )
It was discovered that PostgreSQL had a type confusion issue when functions used internal arguments. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-14680 )
It was discovered that PostgreSQL did not properly enforce GSSAPI encryption when used together with SSL. An attacker could possibly use this issue to perform a machine-in-the-middle attack and obtain sensitive information. This issue only affected Ubuntu 26.04 LTS. ( CVE-2026-14681 )
It was discovered that PostgreSQL allowed SQL injection through EXTRACT arguments during expression deparsing. An authenticated user could possibly use this issue to perform SQL injection attacks. ( CVE-2026-15741 )
It was discovered that PostgreSQL fuzzystrmatch had integer wraparound issues that could write to arbitrary addresses. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-15742 )
It was discovered that PostgreSQL had a type confusion issue in pg_restore_attribute_stats(). An authenticated user could possibly use this issue to execute arbitrary code. This issue only affected Ubuntu 26.04 LTS. ( CVE-2026-16238 )
It was discovered that PostgreSQL had a type confusion issue when handling cursor CLOSE and DECLARE operations. An authenticated user could possibly use this issue to execute arbitrary code. ( CVE-2026-16239 )
It was discovered that PostgreSQL had an integer underflow in the ECPG client library. An attacker could possibly use this issue to cause PostgreSQL to crash, resulting in a denial of service. ( CVE-2026-16241 )
It was discovered that PostgreSQL had an out-of-bounds read in the ascii() function. An authenticated user could possibly use this issue to obtain sensitive information. ( CVE-2026-18024 )
It was discovered that the psql \unrestrict command allowed the superuser of a pg_dump origin server to execute arbitrary code in the psql client. An attacker could possibly use this issue to execute arbitrary code. ( CVE-2026-18408 )
It was discovered that PostgreSQL pg_dump had a heap buffer overflow. An attacker could possibly use this issue to execute arbitrary code. ( CVE-2026-19385 )
This update uses a new upstream release, which includes additional bug fixes. After a standard system update you need to restart PostgreSQL to make all the necessary changes.
The problem can be corrected by updating your system to the following package versions:
Ubuntu Pro provides ten-year security coverage to 25,000+ packages in Main and Universe repositories, and it is free for up to five machines.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
