Skip to content

Vendor

pgbouncer vulnerabilities

10 published CVES affecting pgbouncer, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
10
Critical
2
High
6
Medium
2
Low
0
Unscored
0
CISA KEV
0
Atom feed of pgbouncer alerts

Products

Latest pgbouncer CVEs

Newest publication first

  1. MediumCVSS 4.3 EPSS 0.29%

    PgBouncer before 1.25.2 did not perform an appropriate authorization check for the KILL_CLIENT admin command. All users with access to the administration console (which itself requires authorization) could run this command. It would have been correct to allow only users listed in...

  2. CriticalCVSS 9.8 EPSS 0.37%

    The SCRAM code in PgBouncer before 1.25.2 did not check the return value of strlcat() correctly when building the contents of the SCRAM client-final-message. A malicious backend that sends a SCRAM server-final-message with a long nonce can trigger a stack overflow.

  3. MediumCVSS 5.6 EPSS 2.8%

    A flaw was found in c-ares library, where a missing input validation check of host names returned by DNS (Domain Name Servers) can lead to output of wrong hostnames which might potentially lead to Domain Hijacking. The highest threat from this vulnerability is to confidentiality...

  4. HighCVSS 8.1 EPSS 1.1%

    When PgBouncer is configured to use "cert" authentication, a man-in-the-middle attacker can inject arbitrary SQL queries when a connection is first established, despite the use of TLS certificate verification and encryption. This flaw affects PgBouncer versions prior to 1.16.1.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.