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.
Please note that the PostgreSQL Project does not offer bug bounties.
The PostgreSQL Project is a CVE Numbering Authority (CNA), working with Red Hat as our CNA Root. This allows us to assign our own CVE numbers and publish CVE records for PostgreSQL and closely related projects.
We will currently assign CVE numbers for the following projects upon request to [email protected]:
Additional projects may request inclusion on the list above by emailing [email protected].
NOTE: The security team will only assign CVEs to projects when requested by members of the project. If you think you've found a security issue in a project other than PostgreSQL or it's packages and installers, please contact the security team for that project. See below for more details.
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 security vulnerabilities in PostgreSQL or any of the installers linked from the PostgreSQL download page, please email [email protected].
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 [email protected].
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.
To receive notifications about security releases or other security related news, you can subscribe to the pgsql-announce mailing list. If you set your subscription to only include the tag Security, it will exclude all other announcements that are sent to this list.
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.
You are currently viewing PostgreSQL security vulnerabilities for an unsupported version. If you are still using PostgreSQL 9.5, you should upgrade as soon as possible.
You can filter the view of patches to show just patches for version:
17 -
16 -
15 -
14 -
13
- all
| Reference | Affected | Fixed | Component & CVSS v3 Base Score | Description |
|---|---|---|---|---|
|
CVE-2020-25696 Announcement |
13, 12, 11, 10, 9.6, 9.5 | 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24 | client 7.5 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
psql's \gset allows overwriting specially treated variables more details |
|
CVE-2020-25695 Announcement |
13, 12, 11, 10, 9.6, 9.5 | 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24 | core server 8.8 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Multiple features escape "security restricted operation" sandbox more details |
|
CVE-2020-25694 Announcement |
13, 12, 11, 10, 9.6, 9.5 | 13.1, 12.5, 11.10, 10.15, 9.6.20, 9.5.24 | client 8.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Reconnection can downgrade connection security settings more details |
|
CVE-2020-14350 Announcement |
12, 11, 10, 9.6, 9.5 | 12.4, 11.9, 10.14, 9.6.19, 9.5.23 | core server 7.1 AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H |
Uncontrolled search path element in CREATE EXTENSION more details |
|
CVE-2020-10733 Announcement |
12, 11, 10, 9.6, 9.5 | 12.3, 11.8, 10.13, 9.6.18, 9.5.22 | packaging 6.7 AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H |
Windows installer runs executables from uncontrolled directories more details |
|
CVE-2019-10211 Announcement |
11, 10, 9.6, 9.5, 9.4 | 11.5, 10.10, 9.6.15, 9.5.19, 9.4.24 | packaging 7.8 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Windows installer bundled OpenSSL executes code from unprotected directory more details |
|
CVE-2019-10210 Announcement |
11, 10, 9.6, 9.5, 9.4 | 11.5, 10.10, 9.6.15, 9.5.19, 9.4.24 | packaging 6.7 AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H |
Windows installer writes superuser password to unprotected temporary file more details |
|
CVE-2019-10208 Announcement |
11, 10, 9.6, 9.5, 9.4 | 11.5, 10.10, 9.6.15, 9.5.19, 9.4.24 | core server 7.5 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
TYPE in pg_temp executes arbitrary SQL during SECURITY DEFINER execution more details |
|
CVE-2019-10130 Announcement |
11, 10, 9.6, 9.5 | 11.3, 10.8, 9.6.13, 9.5.17 | core server 3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
Selectivity estimators bypass row security policies more details |
|
CVE-2019-10128 Announcement |
11, 10, 9.6, 9.5, 9.4 | 11.3, 10.8, 9.6.13, 9.5.17, 9.4.22 | packaging 7.0 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
EnterpriseDB Windows installer does not clear permissive ACL entries more details |
|
CVE-2019-10127 Announcement |
11, 10, 9.6, 9.5, 9.4 | 11.3, 10.8, 9.6.13, 9.5.17, 9.4.22 | packaging 7.0 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
BigSQL Windows installer does not clear permissive ACL entries. more details |
|
CVE-2019-3466 Announcement |
12, 11, 10, 9.6, 9.5, 9.4 | 12.1, 11.6, 10.11, 9.6.16, 9.5.20, 9.4.25 | packaging 8.4 AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H |
pg_ctlcluster script in postgresql-common does not drop privileges when creating socket/statistics temporary directories more details |
|
CVE-2018-10925 Announcement |
10, 9.6, 9.5 | 10.5, 9.6.10, 9.5.14 | core server 7.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N |
Memory disclosure and missing authorization in INSERT ... ON CONFLICT DO UPDATE. more details |
|
CVE-2018-10915 Announcement |
10, 9.6, 9.5, 9.4, 9.3 | 10.5, 9.6.10, 9.5.14, 9.4.19, 9.3.24 | client 8.5 AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
Certain host connection parameters defeat client-side security defenses more details |
|
CVE-2018-1058 Announcement |
10, 9.6, 9.5, 9.4, 9.3 | 10.3, 9.6.8, 9.5.12, 9.4.17, 9.3.22 | client 8.8 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Uncontrolled search path element in pg_dump and other client applications more details |
|
CVE-2018-1053 Announcement |
10, 9.6, 9.5, 9.4, 9.3 | 10.2, 9.6.7, 9.5.11, 9.4.16, 9.3.21 | client 6.7 AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H |
pg_upgrade creates file of sensitive metadata under prevailing umask more details |
|
CVE-2017-15099 Announcement |
10, 9.6, 9.5 | 10.1, 9.6.6, 9.5.10 | core server 3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
INSERT ... ON CONFLICT DO UPDATE fails to enforce SELECT privileges more details |
|
CVE-2017-15098 Announcement |
10, 9.6, 9.5, 9.4, 9.3 | 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20 | core server 4.3 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Memory disclosure in JSON functions more details |
|
CVE-2017-12172 Announcement |
10, 9.6, 9.5, 9.4, 9.3, 9.2 | 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, 9.2.24 | contrib module 8.4 AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H |
Start scripts permit database administrator to modify root-owned files more details |
|
CVE-2017-7548 Announcement |
9.6, 9.5, 9.4 | 9.6.4, 9.5.8, 9.4.13 | core server 3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N |
lo_put() function ignores ACLs more details |
|
CVE-2017-7547 Announcement |
9.6, 9.5, 9.4, 9.3, 9.2 | 9.6.4, 9.5.8, 9.4.13, 9.3.18, 9.2.22 | core server 8.5 AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
pg_user_mappings view discloses passwords to users lacking server privileges more details |
|
CVE-2017-7546 Announcement |
9.6, 9.5, 9.4, 9.3, 9.2 | 9.6.4, 9.5.8, 9.4.13, 9.3.18, 9.2.22 | core server 8.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
empty password accepted in some authentication methods more details |
|
CVE-2017-7486 Announcement |
9.6, 9.5, 9.4, 9.3, 9.2 | 9.6.3, 9.5.7, 9.4.12, 9.3.17, 9.2.21 | core server 8.5 AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
pg_user_mappings view discloses foreign server passwords more details |
|
CVE-2017-7485 Announcement |
9.6, 9.5, 9.4, 9.3 | 9.6.3, 9.5.7, 9.4.12, 9.3.17 | client 8.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
libpq ignores PGREQUIRESSL environment variable more details |
|
CVE-2017-7484 Announcement |
9.6, 9.5, 9.4, 9.3, 9.2 | 9.6.3, 9.5.7, 9.4.12, 9.3.17, 9.2.21 | core server 4.3 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
selectivity estimators bypass SELECT privilege checks more details |
|
CVE-2016-7048 Announcement |
9.5, 9.4, 9.3, 9.2, 9.1 | 9.5.5, 9.4.10, 9.3.15, 9.2.19, 9.1.24 | packaging 7.5 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
Interactive installer downloads software over plain HTTP, then executes it more details |
|
CVE-2016-5424 Announcement |
9.5, 9.4, 9.3, 9.2, 9.1 | 9.5.4, 9.4.9, 9.3.14, 9.2.18, 9.1.23 | client 8.5 AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
Exceptional database and role names could enable escalation to superuser more details |
|
CVE-2016-5423 Announcement |
9.5, 9.4, 9.3, 9.2, 9.1 | 9.5.4, 9.4.9, 9.3.14, 9.2.18, 9.1.23 | core server 4.3 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Certain nested CASE/WHEN expressions can crash server more details |
|
CVE-2016-3065 Announcement |
9.5 | 9.5.2 | contrib module 3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
pageinspect does not check permissions for BRIN indexes more details |
|
CVE-2016-2193 Announcement |
9.5 | 9.5.2 | core server 4.2 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N |
Plan cache might use wrong role context for RLS policy more details |
|
CVE-2016-0773 Announcement |
9.5, 9.4, 9.3, 9.2, 9.1 | 9.5.1, 9.4.6, 9.3.11, 9.2.15, 9.1.20 | core server 6.5 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H |
Unchecked regex can crash the server more details |
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.
12 -
11 -
10 -
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:
| Component | Description |
|---|---|
| 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: