PostgreSQL End of Life Dates

Developers rely on PostgreSQL, a free and open-source relational database management system, to manage their data due to its extensibility and SQL compliance. Created to address the need for a robust and flexible database solution, PostgreSQL has been maintained by a global community of developers since its inception. The PostgreSQL Global Development Group, a team of dedicated contributors, ensures the database system stays up-to-date and secure, which is why developers trust it for their projects. With a long history of development, PostgreSQL has become a staple in the database management world, and its widespread adoption is a testament to its reliability and performance.

The end-of-life landscape for PostgreSQL is complex, with 29 versions released to date, of which 24 have reached their end-of-life. Currently, only 5 versions remain active, with the latest stable version being 18.4. Developers should be aware that version 14 is set to expire on 2026-11-12, marking the next significant milestone in the PostgreSQL lifecycle. This follows the expiration of version 13, which occurred on 2025-11-13. Understanding the version lifecycle is crucial for developers to ensure they are using a supported version and to plan their upgrades accordingly.

PostgreSQL's security track record is impressive, with a total of 259 CVEs tracked, although none of them are critical. The most affected version is 18, with 16 CVEs reported. Despite this, the lack of critical vulnerabilities is a positive indicator of the database system's overall security posture. However, developers should still take action to ensure they are running a secure and supported version of PostgreSQL. This includes monitoring the version lifecycle, applying patches and updates, and planning for upgrades to avoid exposure to known vulnerabilities. By taking these proactive steps, developers can minimize their risk and maintain the integrity of their databases.