PostgreSQL 13 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
PostgreSQL 13 reached end of life on 13 Nov 2025. It no longer receives security fixes.
Support timeline
Official dates from the PostgreSQL release process.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 24 Sept 2020 | — |
| End of life | 13 Nov 2025 | 0.7 years ago |
| Latest release | 13.23 · 10 Nov 2025 | final |
The cost of staying: CVEs since end of life
16 PostgreSQL vulnerabilities have been published since 13 Nov 2025. All were fixed in supported branches — 13 received none of them. Source: NVD.
PostgreSQL CVEs published since 13's EOL, by year
0 of the 16 are rated critical · data refreshed 2026-08-09
Published 12 Feb 2026 · rated high — fixed in supported branches only, never in 13. Details
Published 12 Feb 2026 · rated high — fixed in supported branches only, never in 13. Details
Published 12 Feb 2026 · rated high — fixed in supported branches only, never in 13. Details
Where to go from 13
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 13 still safe to use?
No. PostgreSQL 13 stopped receiving security fixes on 13 Nov 2025. Since then, 16 PostgreSQL vulnerabilities have been published and fixed in supported branches — PostgreSQL 13 received none of those fixes.
Can I still download PostgreSQL 13?
Yes — the final release (13.23) 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 13 to?
Upgrade to PostgreSQL 18, the newest actively supported branch (supported until 14 Nov 2030).