PostgreSQL 13 · Version Status
PostgreSQL 13 End of Life Date
PostgreSQL 13 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
PostgreSQL 13 is past end of life. This version no longer receives security patches. 222 days past EOL — migrate to a supported version immediately.
EOL Date
Nov 13, 2025
222 days past EOL
Latest Release
13.23
Standard release
Release Date
Sep 24, 2020
PostgreSQL 13 series
Attack Surface
30/30 Critical tier
CISA KEV Exposure
20/20 Yes — CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended PostgreSQL 13 support is available
Commercial vendors offer security patches beyond EOL — compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 6.3 |
6.3.2 |
Mar 1, 2003 |
EOL |
| 6.4 |
6.4.2 |
Oct 30, 2003 |
EOL |
| 6.5 |
6.5.3 |
Jun 9, 2004 |
EOL |
| 7.0 |
7.0.3 |
May 8, 2005 |
EOL |
| 7.1 |
7.1.3 |
Apr 13, 2006 |
EOL |
| 7.2 |
7.2.8 |
Feb 4, 2007 |
EOL |
| 7.3 |
7.3.21 |
Nov 27, 2007 |
EOL |
| 7.4 |
7.4.30 |
Oct 1, 2010 |
EOL |
What does PostgreSQL 13 end of life mean?
When PostgreSQL 13 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running PostgreSQL 13 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to PostgreSQL 18 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does PostgreSQL 13 reach end of life?
PostgreSQL 13 reached end of life on November 13, 2025. This version is no longer receiving security patches.
Is PostgreSQL 13 still supported?
No. PostgreSQL 13 reached end of life on November 13, 2025 and is no longer receiving security patches.
What should I upgrade to from PostgreSQL 13?
The recommended upgrade from PostgreSQL 13 is
PostgreSQL 18 — the latest actively supported version. Check the
PostgreSQL full timeline for all supported versions.
What are the security risks of running PostgreSQL 13 past EOL?
When PostgreSQL 13 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL PostgreSQL should migrate immediately or implement compensating controls.
Does PostgreSQL track end-of-life by point release (e.g. PostgreSQL 18.1, PostgreSQL 18.2)?
No — PostgreSQL end-of-life dates apply to the entire 18.x release series, not individual point releases. A point release like PostgreSQL 18.1 or PostgreSQL 18.2 shares the same EOL date as PostgreSQL 18. Security patches stop for the entire 18.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.