Postgresql 16 · Version Status
Postgresql 16 End of Life Date
Postgresql 16 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Postgresql 16 is actively supported. EOL date: November 9, 2028.
EOL Date
Nov 9, 2028
915 days remaining
Latest Release
16.13
Standard release
Release Date
Sep 14, 2023
Postgresql 16 series
| 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 16 end of life mean?
When Postgresql 16 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 16 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 16 reach end of life?
Postgresql 16 reached end of life on November 9, 2028. That is 915 days remaining.
Is Postgresql 16 still supported?
Yes, Postgresql 16 is currently supported. The EOL date is November 9, 2028.
What should I upgrade to from Postgresql 16?
The recommended upgrade from Postgresql 16 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 16 past EOL?
When Postgresql 16 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.