Regarding security vulnerabilities, three CVEs were identified:
1. CVE-2025-8713: Allows unauthorized users to access sampled data through optimizer statistics.
2. CVE-2025-8714: Enables a superuser to execute arbitrary code on the psql client during pg_dump operations.
3. CVE-2025-8715: Similar to CVE-2025-8714, but involves newline characters in object names, allowing code injection during restores.
PostgreSQL 13 will reach its end of life on November 13, 2025, and users are encouraged to upgrade to more current versions. The release also emphasizes that PostgreSQL 18 Beta 3 is open for community testing, with a general availability expected in September/October 2025.
To upgrade to PostgreSQL 18 Beta 3, users must follow a process similar to major version upgrades, utilizing pg_upgrade or pg_dump/pg_restore. The PostgreSQL community is invited to test this beta version with their applications to help identify bugs and ensure stability before the final release.
Overall, this update is essential for users to maintain the security, performance, and reliability of their PostgreSQL installations. The active involvement of the community in testing and providing feedback is crucial for the successful launch of PostgreSQL 18.
In conclusion, PostgreSQL continues to enhance its database offerings with regular updates, security fixes, and new features, ensuring it remains a robust option for relational database management. Users should stay informed about upcoming releases and participate in testing to further strengthen the software's reliability
PostgreSQL 17.6, 16.10, 15.14, 14.19, 13.22, and 18 Beta 3 released
PostgreSQL has released an update for all supported versions, including 17.6, 16.10, 15.14, 14.19, 13.22, and the third beta release of PostgreSQL 18. This release fixes three security vulnerabilities and over 55 bugs reported over the last several months.
The update fixes over 55 bugs reported in the last several months, including fixes for BRIN indexes using the numeric_minmax_multi_ops operator class, logical replication, premature removal of old WAL during a checkpoint, reverting a change that could reject XML documents over 10MB in size, handling nested character classes in SIMILAR TO expressions, restoring the ability for PL/pgSQL expressions to use parallel execution, avoiding a rare scenario where a B-tree index could modify the wrong entry, and addressing issues with MERGE, LZ4 decompression failure, and timing-dependent connection failures.PostgreSQL 17.6, 16.10, 15.14, 14.19, 13.22, and 18 Beta 3 released @ Linux Compatible