Security Information

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.

CVE Numbering Authority

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

Additional projects may request inclusion on the list above by emailing

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.

What is a Security Vulnerability in PostgreSQL?

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 mailing lists. This is by design.

Reporting a PostgreSQL Security Vulnerability

For security vulnerabilities in PostgreSQL or any of the installers linked from the PostgreSQL download page, please email

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

Reporting non-PostgreSQL Security Vulnerabilities

Please see below for how you can report security vulnerabilities in PostgreSQL-related projects:

PostgreSQL Security Releases

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.

PostgreSQL Security Notifications

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.

Known PostgreSQL Security Vulnerabilities

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:

  • Which major versions a security vulnerability is present in
  • Which minor version update releases a security vulnerability is fixed in
  • Whether an exploit requires a valid login
  • CVSS score

You can find more detailed information about a security vulnerability by clicking on the links in the table below.

Known PostgreSQL Security Vulnerabilities in PostgreSQL 16

You can filter the view of patches to show just patches for version:
16 - 15 - 14 - 13 - 12 - all

Reference Affected Fixed Component & CVSS v3 Base Score Description
16, 15, 14 16.3, 15.7, 14.12 core server
Restrict visibility of "pg_stats_ext" and "pg_stats_ext_exprs" entries to the table owner

more details
16, 15, 14, 13, 12 16.2, 15.6, 14.11, 13.14, 12.18 core server

more details
16, 15, 14, 13, 12, 11 16.1, 15.5, 14.10, 13.13, 12.17, 11.22 core server
Role "pg_signal_backend" can signal certain superuser processes

more details
16, 15, 14, 13, 12, 11 16.1, 15.5, 14.10, 13.13, 12.17, 11.22 core server
Buffer overrun from integer overflow in array modification

more details
16, 15, 14, 13, 12, 11 16.1, 15.5, 14.10, 13.13, 12.17, 11.22 core server
Memory disclosure in aggregate function calls

more details

Unsupported versions

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

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:

  • Álvaro Herrera
  • Andres Freund
  • Andrew Dunstan
  • Bruce Momjian
  • Dave Page
  • Greg Stark
  • Heikki Linnakangas
  • Joe Conway
  • Jonathan Katz
  • Magnus Hagander
  • Michael Paquier
  • Nathan Bossart
  • Noah Misch
  • Peter Eisentraut
  • Robert Haas
  • Stefan Kaltenbrunner
  • Tom Lane