Aggregates CVE and security vulnerability intelligence across all pgbouncer-related products, including CVSS, EPSS, publication dates, and vulnerability intelligence data.
Disclosed issues often relate to vendor risk buffer overflow, vendor risk memory corruption, and vendor risk sql injection; exposure may include vendor impact application crash in vendor surface software deployment contexts.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2026-6667 | 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 the admin_users parameter. | f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 | 4.3 | 0.01% | 2026-05-09 | 2026-05-14 |
| CVE-2026-6666 | A possible null pointer reference in PgBouncer before 1.25.2 could lead to a crash, if a server sends an error response without SQLSTATE field. | f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 | 5.9 | 0.01% | 2026-05-09 | 2026-05-14 |
| CVE-2026-6665 | 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. | f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 | 8.1 | 0.02% | 2026-05-09 | 2026-05-14 |
| CVE-2026-6664 | An integer overflow in network packet parsing code in PgBouncer before 1.25.2 bypasses a boundary check and can lead to a crash. An unauthenticated remote attacker can crash PgBouncer with a malformed SCRAM authentication packet. | f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 | 7.5 | 0.04% | 2026-05-09 | 2026-05-14 |
| CVE-2025-12819 | Untrusted search path in auth_query connection handler in PgBouncer before 1.25.1 allows an unauthenticated attacker to execute arbitrary SQL during authentication via a malicious search_path parameter in the StartupMessage. | f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 | 7.5 | 0.17% | 2025-12-03 | 2025-12-27 |
| CVE-2025-2291 | Password can be used past expiry in PgBouncer due to auth_query not taking into account Postgres its VALID UNTIL value, which allows an attacker to log in with an already expired password | f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 | 8.1 | 0.06% | 2025-04-16 | 2025-12-08 |
| CVE-2021-3672 | 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 and integrity as well as system availability. | [email protected] | 5.6 | 0.04% | 2021-11-23 | 2024-11-21 |
| CVE-2021-3935 | 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. | [email protected] | 8.1 | 0.14% | 2021-11-22 | 2025-11-03 |
| CVE-2015-6817 | PgBouncer 1.6.x before 1.6.1, when configured with auth_user, allows remote attackers to gain login access as auth_user via an unknown username. | [email protected] | 8.1 | 1.37% | 2017-05-23 | 2026-05-13 |
| CVE-2015-4054 | PgBouncer before 1.5.5 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) by sending a password packet before a startup packet. | [email protected] | 7.5 | 3.38% | 2017-05-23 | 2026-05-13 |