The PostgreSQL Global Development Group (PGDG) takes security seriously. This allows our users to place their trust in PostgreSQL for protecting their mission-critical data.
The PostgreSQL Global Development Group follows a model that shares responsibility between PostgreSQL itself and its deployment environment, including hardware, operating system, and the application layer (programming language, frameworks and client libraries). The PostgreSQL documentation provides info on the inherent security features of PostgreSQL and how to securely configure and run PostgreSQL.
Security vulnerabilities can exist both in PostgreSQL and software within the PostgreSQL ecosystem, including client libraries, extensions, installers, and other utilities. This page walks through what is considered a security vulnerability in PostgreSQL, how to report PostgreSQL security vulnerabilities, and how fixes for security vulnerabilities are released.
A security vulnerability in PostgreSQL is an issue that allows a user to gain access to privileges or data that they do not have permission to use, or allows a user to execute arbitrary code through a PostgreSQL process.
The PostgreSQL Security Team does not consider reports on actions a PostgreSQL superuser takes to be a security vulnerability. However, a report on an unprivileged user escalating to superuser generally qualifies as valid.
The PostgreSQL Security Team typically does not consider a denial-of-service on a PostgreSQL server from an authenticated, valid SQL statement to be a security vulnerability. A denial-of-service issue of this nature could still be a bug, and we encourage you to report it on the Report a Bug page.
Please do not report the lack of DMARC on postgresql.org mailing lists. This is by design.
For reporting non-security bugs, please visit the Report a Bug page.
If you are unsure if an issue is a security vulnerability, please err on the side of caution and email firstname.lastname@example.org.
Please see below for how you can report security vulnerabilities in PostgreSQL-related projects:
The PostgreSQL Project releases security fixes as part of minor version updates. You are always advised to use the latest minor version available, as it will contain other non-security related fixes.
A new PostgreSQL major release, which contains new features, has every prior security fix.
If you find a security vulnerability in PostgreSQL, the PostgreSQL Security Team will credit you in the release notes and register a CVE for the vulnerability. Please do not register a CVE independently of the PostgreSQL Security Team.
The PostgreSQL Security Team does not file a CVE for vulnerabilities in PostgreSQL-related projects nor does it list those vulnerabilities in the section below. It is up to external project maintainers to register a CVE for a security vulnerability.
The PostgreSQL Global Development Group 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 security vulnerabilities over a range of criteria. This includes:
You can find more detailed information about a security vulnerability by clicking on the links in the table below.
|Reference||Affected||Fixed||Component & CVSS v3 Base Score||Description|
|14, 13, 12, 11, 10||14.3, 13.7, 12.11, 11.16, 10.21||core server
|Autovacuum, REINDEX, and others omit "security restricted operation" sandbox
|14, 13, 12, 11, 10, 9.6||14.1, 13.5, 12.9, 11.14, 10.19, 9.6.24||client
|libpq processes unencrypted bytes from man-in-the-middle
|14, 13, 12, 11, 10, 9.6||14.1, 13.5, 12.9, 11.14, 10.19, 9.6.24||core server
|Server processes unencrypted bytes from man-in-the-middle
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.6 - 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.|
The PostgreSQL Security Team is made up of a group of contributors to the PostgreSQL project who have experience in different aspects of database and information security.
You can find a list of members on the security team here: