Complete end-of-life dates, support windows, and security status for all Postgresql versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 6.3 | 6.3.2 | Mar 1, 1998 | Mar 1, 2003 | 8470 days past EOL | EOL |
| 6.4 | 6.4.2 | Oct 30, 1998 | Oct 30, 2003 | 8227 days past EOL | EOL |
| 6.5 | 6.5.3 | Jun 9, 1999 | Jun 9, 2004 | 8004 days past EOL | EOL |
| 7.0 | 7.0.3 | May 8, 2000 | May 8, 2005 | 7671 days past EOL | EOL |
| 7.1 | 7.1.3 | Apr 13, 2001 | Apr 13, 2006 | 7331 days past EOL | EOL |
| 7.2 | 7.2.8 | Feb 4, 2002 | Feb 4, 2007 | 7034 days past EOL | EOL |
| 7.3 | 7.3.21 | Nov 27, 2002 | Nov 27, 2007 | 6738 days past EOL | EOL |
| 7.4 | 7.4.30 | Nov 17, 2003 | Oct 1, 2010 | 5699 days past EOL | EOL |
| 8.0 | 8.0.26 | Jan 19, 2005 | Oct 1, 2010 | 5699 days past EOL | EOL |
| 8.1 | 8.1.23 | Nov 8, 2005 | Nov 8, 2010 | 5661 days past EOL | EOL |
| 8.2 | 8.2.23 | Dec 5, 2006 | Dec 5, 2011 | 5269 days past EOL | EOL |
| 8.3 | 8.3.23 | Feb 4, 2008 | Feb 7, 2013 | 4839 days past EOL | EOL |
| 8.4 | 8.4.22 | Jul 1, 2009 | Jul 24, 2014 | 4307 days past EOL | EOL |
| 9.0 | 9.0.23 | Sep 20, 2010 | Oct 8, 2015 | 3866 days past EOL | EOL |
| 9.1 | 9.1.24 | Sep 12, 2011 | Oct 27, 2016 | 3481 days past EOL | EOL |
| 9.2 | 9.2.24 | Sep 10, 2012 | Nov 9, 2017 | 3103 days past EOL | EOL |
| 9.3 | 9.3.25 | Sep 9, 2013 | Nov 8, 2018 | 2739 days past EOL | EOL |
| 9.4 | 9.4.26 | Dec 18, 2014 | Feb 13, 2020 | 2277 days past EOL | EOL |
| 9.5 | 9.5.25 | Jan 7, 2016 | Feb 11, 2021 | 1913 days past EOL | EOL |
| 9.6 | 9.6.24 | Sep 29, 2016 | Nov 11, 2021 | 1640 days past EOL | EOL |
| 10 | 10.23 | Oct 5, 2017 | Nov 10, 2022 | 1276 days past EOL | EOL |
| 11 | 11.22 | Oct 18, 2018 | Nov 9, 2023 | 912 days past EOL | EOL |
| 12 | 12.22 | Oct 3, 2019 | Nov 21, 2024 | 534 days past EOL | EOL |
| 13 | 13.23 | Sep 24, 2020 | Nov 13, 2025 | 177 days past EOL | EOL |
| 14 | 14.22 | Sep 30, 2021 | Nov 12, 2026 | 187 days remaining | Active |
| 15 | 15.17 | Oct 13, 2022 | Nov 11, 2027 | 551 days remaining | Active |
| 16 | 16.13 | Sep 14, 2023 | Nov 9, 2028 | 915 days remaining | Active |
| 17 | 17.9 | Sep 26, 2024 | Nov 8, 2029 | 1279 days remaining | Active |
| 18 | 18.3 | Sep 25, 2025 | Nov 14, 2030 | 1650 days remaining | Active |
When a Postgresql version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Postgresql should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →