PostgreSQL 17 · Version Status
PostgreSQL 17 End of Life Date
PostgreSQL 17 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
PostgreSQL 17 is actively supported. EOL date: November 8, 2029.
📅 Get reminded before PostgreSQL 17 reaches EOL on November 8, 2029 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Nov 8, 2029
1142 days remaining
Latest Release
17.11
Standard release
Release Date
Sep 26, 2024
PostgreSQL 17 series
Lifecycle detail
PostgreSQL 17 was released on September 26, 2024 and support is scheduled to end on November 8, 2029 — a planned supported lifespan of 5 years and 1 month, in line with the 5 years and 1 month median for PostgreSQL releases. Its most recent patch is 17.11, published August 10, 2026.
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 →
| 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 17 end of life mean?
When PostgreSQL 17 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running PostgreSQL 17 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to PostgreSQL 18 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does PostgreSQL 17 reach end of life?
PostgreSQL 17 reached end of life on November 8, 2029. That is 1142 days remaining.
Is PostgreSQL 17 still supported?
Yes, PostgreSQL 17 is currently supported. The EOL date is November 8, 2029.
What should I upgrade to from PostgreSQL 17?
The recommended upgrade from PostgreSQL 17 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 17 past EOL?
When PostgreSQL 17 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. 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.