PostgreSQL 6.0 · Version Status
PostgreSQL 6.0 End of Life Date
PostgreSQL 6.0 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 6.0 is past end of life. This version no longer receives security patches. Past EOL — migrate to a supported version immediately.
EOL Date
date not published
Past EOL
Latest Release
6.0
Standard release
Release Date
Jan 29, 1997
PostgreSQL 6.0 series
Where these dates come from
ReleaseJan 29, 1997endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
PostgreSQL 6.0 was released on January 29, 1997. Its most recent patch is 6.0, published January 29, 1997.
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.0 |
6.0 |
Supported |
EOL |
| 6.1 |
6.1.1 |
Supported |
EOL |
| 6.2 |
6.2.1 |
Supported |
EOL |
| 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 |
What does PostgreSQL 6.0 end of life mean?
When PostgreSQL 6.0 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 6.0 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 6.0 reach end of life?
PostgreSQL 6.0 has already reached end of life, though the vendor has not published an exact date.
Is PostgreSQL 6.0 still supported?
No. PostgreSQL 6.0 reached end of life on an unpublished date and is no longer receiving security patches.
What should I upgrade to from PostgreSQL 6.0?
The recommended upgrade from PostgreSQL 6.0 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 6.0 past EOL?
Since PostgreSQL 6.0 reached end of life, the maintainers no longer issue 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.