PostgreSQL 10 · Version Status
PostgreSQL 10 End of Life Date
PostgreSQL 10 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 10 is past end of life. This version no longer receives security patches. 1458 days past EOL — migrate to a supported version immediately.
EOL Date
Nov 10, 2022
1458 days past EOL
Latest Release
10.23
Standard release
Release Date
Oct 5, 2017
PostgreSQL 10 series
Where these dates come from
End of lifeNov 10, 2022Vendor's own page, read by our adapter · postgresql.org · checked Nov 3, 2026high · 3 sources agree ReleaseOct 5, 2017Vendor's own page, read by our adapter · postgresql.org · checked Nov 3, 2026high · 3 sources agree 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 10 was released on October 5, 2017 and support ended on November 10, 2022 — a supported lifespan of 5 years and 1 month, in line with the 5 years and 1 month median for PostgreSQL releases. Its latest release on record is 10.23, published November 7, 2022 — 3 days before support ended. It has been past its end-of-life date for 4 years. 3 newer PostgreSQL releases have shipped since.
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 10 end of life mean?
When PostgreSQL 10 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 10 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 10 reach end of life?
PostgreSQL 10 reached end of life on November 10, 2022. This version is no longer receiving security patches.
Is PostgreSQL 10 still supported?
No. PostgreSQL 10 reached end of life on November 10, 2022 and is no longer receiving security patches.
What should I upgrade to from PostgreSQL 10?
The recommended upgrade from PostgreSQL 10 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 10 past EOL?
Since PostgreSQL 10 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.