The PostgreSQL Global Development Group (PGDG) takes security seriously, allowing our users to place their trust in the web sites and applications built around PostgreSQL. Our approach covers fail-safe configuration options, a secure and robust database server as well as good integration with other security infrastructure software.
PostgreSQL security updates are primarily made available as minor version upgrades. You are always advised to use the latest minor version available, as it will likely also contain other non-security related fixes. All known security issues are always fixed in the next major release, when it comes out.
PGDG believes that accuracy, completeness and availability of security information is essential for our users. We choose to pool all information on this one page, allowing easy searching for vulnerabilities by a range of criteria.
Vulnerabilities list which major releases they were present in, and which version they are fixed in for each. If the vulnerability was exploitable without a valid login, this is also stated. They also list a vulnerability class, but we urge all users to read the description to determine if the bug affects specific installations or not.
|Reference||Affected||Fixed||Component & CVSS v3 Base Score||Description|
You can also view archived security patches for unsupported versions. Note that no further
security patches are made available for these versions as they are end of life.
9.5 - 9.4 - 9.3 - 9.2 - 9.1 - 9.0 - 8.4 - 8.3 - 8.2 - 8.1 - 8.0 - 7.4 - 7.3
The following component references are used in the above table:
|core server||This vulnerability exists in the core server product.|
|client||This vulnerability exists in a client library or client application only.|
|contrib module||This vulnerability exists in a contrib module. Contrib modules are not installed by default when PostgreSQL is installed from source. They may be installed by binary packages.|
|client contrib module||This vulnerability exists in a contrib module used on the client only.|
|packaging||This vulnerability exists in PostgreSQL binary packaging, e.g. an installer or RPM.|