PostgreSQL · Lifecycle Status

PostgreSQL End of Life (EOL) Dates & Support Timeline

Q: What is the end-of-life date for PostgreSQL?

The next PostgreSQL version reaching EOL is 14 on November 12, 2026. See the full table above for all version EOL dates.

Q: When is the PostgreSQL support end date?

The next PostgreSQL support end date is November 12, 2026, when version 14 reaches end of support. Each version has its own support end date — see the table above for every version's date.

Q: What is the latest supported version of PostgreSQL?

The latest active version of PostgreSQL is 18.4. Always verify against the table above as support windows can change.

Q: 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.

Complete end-of-life dates, support windows, and security status for all PostgreSQL versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

📅 Get reminded before PostgreSQL 14 reaches EOL on November 12, 2026 — alerts 90, 30 & 7 days out.

Google →

Latest Active

18.4

18 series

Next EOL

Nov 12, 2026

Active Versions

of 29 total

EOL Versions

no longer patched

Critical Risk

EOL Risk Score™ How is this calculated? →

EOL Recency

30/40

Attack Surface

30/30 Critical tier

CISA KEV Exposure

20/20 Yes — CISA 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 →

Release Cycle Timeline

■ EOL ■ Warning ■ Active ┊ Today

All Versions

Version	Latest Release	Release Date	EOL Date	Days	Status
6.3	6.3.2	Mar 1, 1998	Mar 1, 2003	8535 days past EOL	EOL
6.4	6.4.2	Oct 30, 1998	Oct 30, 2003	8292 days past EOL	EOL
6.5	6.5.3	Jun 9, 1999	Jun 9, 2004	8069 days past EOL	EOL
7.0	7.0.3	May 8, 2000	May 8, 2005	7736 days past EOL	EOL
7.1	7.1.3	Apr 13, 2001	Apr 13, 2006	7396 days past EOL	EOL
7.2	7.2.8	Feb 4, 2002	Feb 4, 2007	7099 days past EOL	EOL
7.3	7.3.21	Nov 27, 2002	Nov 27, 2007	6803 days past EOL	EOL
7.4	7.4.30	Nov 17, 2003	Oct 1, 2010	5764 days past EOL	EOL
8.0	8.0.26	Jan 19, 2005	Oct 1, 2010	5764 days past EOL	EOL
8.1	8.1.23	Nov 8, 2005	Nov 8, 2010	5726 days past EOL	EOL
8.2	8.2.23	Dec 5, 2006	Dec 5, 2011	5334 days past EOL	EOL
8.3	8.3.23	Feb 4, 2008	Feb 7, 2013	4904 days past EOL	EOL
8.4	8.4.22	Jul 1, 2009	Jul 24, 2014	4372 days past EOL	EOL
9.0	9.0.23	Sep 20, 2010	Oct 8, 2015	3931 days past EOL	EOL
9.1	9.1.24	Sep 12, 2011	Oct 27, 2016	3546 days past EOL	EOL
9.2	9.2.24	Sep 10, 2012	Nov 9, 2017	3168 days past EOL	EOL
9.3	9.3.25	Sep 9, 2013	Nov 8, 2018	2804 days past EOL	EOL
9.4	9.4.26	Dec 18, 2014	Feb 13, 2020	2342 days past EOL	EOL
9.5	9.5.25	Jan 7, 2016	Feb 11, 2021	1978 days past EOL	EOL
9.6	9.6.24	Sep 29, 2016	Nov 11, 2021	1705 days past EOL	EOL
10	10.23	Oct 5, 2017	Nov 10, 2022	1341 days past EOL	EOL
11	11.22	Oct 18, 2018	Nov 9, 2023	977 days past EOL	EOL
12	12.22	Oct 3, 2019	Nov 21, 2024	599 days past EOL	EOL
13	13.23	Sep 24, 2020	Nov 13, 2025	242 days past EOL	EOL
14	14.23	Sep 30, 2021	Nov 12, 2026	122 days remaining	Warning
15	15.18	Oct 13, 2022	Nov 11, 2027	486 days remaining	Active
16	16.14	Sep 14, 2023	Nov 9, 2028	850 days remaining	Active
17	17.10	Sep 26, 2024	Nov 8, 2029	1214 days remaining	Active
18	18.4	Sep 25, 2025	Nov 14, 2030	1585 days remaining	Active

What does PostgreSQL end of life mean for your organization?

When a version of PostgreSQL reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL PostgreSQL should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL PostgreSQL versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai

Get PostgreSQL Support Options

PostgreSQL has 24 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.

Get My Support Options →

Frequently Asked Questions

What is the end-of-life date for PostgreSQL?

The next PostgreSQL version reaching EOL is 14 on November 12, 2026. See the full table above for all version EOL dates.

When is the PostgreSQL support end date?

The next PostgreSQL support end date is November 12, 2026, when version 14 reaches end of support. Each version has its own support end date — see the table above for every version's date.

What is the latest supported version of PostgreSQL?

The latest active version of PostgreSQL is 18.4. Always verify against the table above as support windows can change.

What happens when PostgreSQL reaches end of life?

When PostgreSQL reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.

How do I check if I'm running an EOL version of PostgreSQL?

Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.

Is there extended support available for EOL PostgreSQL versions?

Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

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

→

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →