Postgresql 10 · Version Status
Postgresql 10 End of Life Date
Postgresql 10 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Postgresql 10 is past end of life. This version no longer receives security patches. 1276 days past EOL — migrate to a supported version immediately.
EOL Date
Nov 10, 2022
1276 days past EOL
Latest Release
10.23
Standard release
Release Date
Oct 5, 2017
Postgresql 10 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 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Postgresql 10 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 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?
When Postgresql 10 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.