PostgreSQL 7.0 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
PostgreSQL 7.0 reached end of life on 8 May 2005. It no longer receives security fixes.
Support timeline
Official dates from the PostgreSQL release process.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 8 May 2000 | — |
| End of life | 8 May 2005 | 21.3 years ago |
| Latest release | 7.0.3 · 12 Nov 2000 | final |
The cost of staying: CVEs since end of life
159 PostgreSQL vulnerabilities have been published since 8 May 2005. All were fixed in supported branches — 7.0 received none of them. Source: NVD.
PostgreSQL CVEs published since 7.0's EOL, by year
7 of the 159 are rated critical · data refreshed 2026-08-09
Published 16 Aug 2017 · rated critical — fixed in supported branches only, never in 7.0. Details
Published 13 Nov 2018 · rated critical — fixed in supported branches only, never in 7.0. Details
Published 29 Oct 2019 · rated critical — fixed in supported branches only, never in 7.0. Details
Where to go from 7.0
Recommended target: PostgreSQL 18 (supported until 14 Nov 2030).
The newest actively supported branch is PostgreSQL 18 (latest release 18.4). Review postgresql.org before upgrading.
Frequently asked questions
Is PostgreSQL 7.0 still safe to use?
No. PostgreSQL 7.0 stopped receiving security fixes on 8 May 2005. Since then, 159 PostgreSQL vulnerabilities have been published and fixed in supported branches — PostgreSQL 7.0 received none of those fixes.
Can I still download PostgreSQL 7.0?
Yes — the final release (7.0.3) generally remains available from vendor archives and OS package mirrors, but installing it means running software with known, unpatched vulnerabilities.
What should I upgrade PostgreSQL 7.0 to?
Upgrade to PostgreSQL 18, the newest actively supported branch (supported until 14 Nov 2030).