PostgreSQL versions
PostgreSQL: update to 18.7, 17.12, 16.16 or 15.20. Our data lists no newest release and no fix for 19. 14 and older have reached end of life in the lifecycle data.
Data: .
Which PostgreSQL branch to run
The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.
| Branch | Status | Newest safe release | Upgrade to |
|---|---|---|---|
| 19 | Fixes until 19 November 2031 | Newest release not in our data | Newest release not in our data |
| 1898 CVE records that this page reads | Fixes until 14 November 2030 | 18.7 | 18.7 (this branch) |
| 1796 CVE records that this page reads | Fixes until 8 November 2029 | 17.12 | 17.12 (this branch) |
| 1694 CVE records that this page reads | Fixes until 9 November 2028 | 16.16 | 16.16 (this branch) |
| 1590 CVE records that this page reads | Fixes until 11 November 2027 | 15.20 | 15.20 (this branch) |
| 1489 CVE records that this page reads | Ended on 12 November 2026 | None, the branch has ended | 15.20 (move to 15) |
| 1312 CVE records that this page reads | Ended on 13 November 2025 | None, the branch has ended | 15.20 (move to 15) |
| 126 CVE records that this page reads | Ended on 21 November 2024 | None, the branch has ended | 15.20 (move to 15) |
| 11 | Ended on 9 November 2023 | None, the branch has ended | 15.20 (move to 15) |
| 10 | Ended on 10 November 2022 | None, the branch has ended | 15.20 (move to 15) |
| 9.6 | Ended on 11 November 2021 | None, the branch has ended | 15.20 (move to 15) |
| 9.5 | Ended on 11 February 2021 | None, the branch has ended | 15.20 (move to 15) |
| 9.4 | Ended on 13 February 2020 | None, the branch has ended | 15.20 (move to 15) |
| 9.3 | Ended on 8 November 2018 | None, the branch has ended | 15.20 (move to 15) |
| 9.2 | Ended on 9 November 2017 | None, the branch has ended | 15.20 (move to 15) |
| 9.1 | Ended on 27 October 2016 | None, the branch has ended | 15.20 (move to 15) |
| 9.0 | Ended on 8 October 2015 | None, the branch has ended | 15.20 (move to 15) |
| 8.4 | Ended on 24 July 2014 | None, the branch has ended | 15.20 (move to 15) |
| 8.3 | Ended on 7 February 2013 | None, the branch has ended | 15.20 (move to 15) |
| 8.2 | Ended on 5 December 2011 | None, the branch has ended | 15.20 (move to 15) |
| 8.1 | Ended on 8 November 2010 | None, the branch has ended | 15.20 (move to 15) |
| 8.0 | Ended on 1 October 2010 | None, the branch has ended | 15.20 (move to 15) |
| 7.4 | Ended on 1 October 2010 | None, the branch has ended | 15.20 (move to 15) |
| 7.3 | Ended on 27 November 2007 | None, the branch has ended | 15.20 (move to 15) |
| 7.2 | Ended on 4 February 2007 | None, the branch has ended | 15.20 (move to 15) |
| 7.1 | Ended on 13 April 2006 | None, the branch has ended | 15.20 (move to 15) |
| 7.0 | Ended on 8 May 2005 | None, the branch has ended | 15.20 (move to 15) |
| 6.5 | Ended on 9 June 2004 | None, the branch has ended | 15.20 (move to 15) |
| 6.4 | Ended on 30 October 2003 | None, the branch has ended | 15.20 (move to 15) |
| 6.3 | Ended on 1 March 2003 | None, the branch has ended | 15.20 (move to 15) |
| 6.2 | Ended, date not known | None, the branch has ended | 15.20 (move to 15) |
| 6.1 | Ended, date not known | None, the branch has ended | 15.20 (move to 15) |
| 6.0 | Ended, date not known | None, the branch has ended | 15.20 (move to 15) |
Exploited, or likely to be
CVE records for PostgreSQL that CISA lists as exploited, that have a public exploit, or that EPSS rates 0.50 or more, with the release that fixes each in every branch.
| Record | Signs of exploitation | Fixed in |
|---|---|---|
| CVE-2025-1094PostgreSQL quoting APIs miss neutralizing quoting syntax in text that fails encoding validation8.1 High · published 13 February 2025 | Metasploit module EPSS 0.50 or more | Fixed in 17.3, 16.7, 15.11, 14.16, 13.19 |
What this page counts
The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.
This page reads 110 CVE records that PostgreSQL's own CVE Numbering Authority published and that name PostgreSQL. The fixes are from the 109 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.
No release of a branch that has ended is called safe here. Some of these branches are still named by records published after they ended; the page of each says how many.
Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.
1 record is not placed on a branch, so no branch or release row counts it: CVE-2025-8715.
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)