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.
📅 Get reminded before PostgreSQL 16 reaches EOL on November 9, 2028 — alerts 90, 30 & 7 days out.
Google →
EOL Date
Nov 9, 2028
823 days remaining
Latest Release
16.14
Standard release
Release Date
Sep 14, 2023
PostgreSQL 16 series
Lifecycle detail

PostgreSQL 16 was released on September 14, 2023 and support is scheduled to end on November 9, 2028 — a planned supported lifespan of 5 years and 2 months, in line with the 5 years and 1 month median for PostgreSQL releases. Its most recent patch is 16.14, published May 11, 2026.

← PostgreSQL 15 All PostgreSQL versions PostgreSQL 17 →
30 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
30/30 Critical tier
CISA KEV Exposure
0/20 Not in 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 →
All PostgreSQL Versions
VersionLatestEOL DateStatus
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 823 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.
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.
Deep Dive
Full Guide
PostgreSQL End of Life: Complete Version Support and EOL Dates
→
Data from endoflife.date API · Generated at build time · How we source data →
Related Products
MySQLMariaDBPythonDjango