2026-10-14 - PgBouncer 1.26.1 - "Only startup once" Security Fix CVE-2026-107350: PgBouncer 1.17.0 through 1.26.0 processed a second StartupMessage sent during SCRAM authentication when the client connected to a non-existent database. An attacker knowing the password of a user listed in auth_file could use this to log in as any other user that authenticates using SCRAM, including admins and backen…
2026-09-23 - PgBouncer 1.26.0 - "Ignore all previous search_path" Security Fix CVE-2026-19888: PgBouncer before 1.26.0 did not check that the SCRAM client-final-message contained a nonce. An unauthenticated remote attacker could crash PgBouncer by sending a client-final-message without one. This also applies to users that do not exist, because PgBouncer runs a mock SCRAM exchange for those. This b…
2026-05-08 - PgBouncer 1.25.2 - "Human touch with fresh twist in title race full of uncertainties" Security Fix 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. Fix CVE-2026-6665: The SCRAM code in PgBoun…
2025-12-03 - PgBouncer 1.25.1 - "Fixing a bunch of bugs before Christmas" Security Fix CVE-2025-12819: Before this release it was possible for an unauthenticated attacker to execute arbitrary SQL during authentication by providing a malicious search_path parameter in the StartupMessage. Systems that have ALL the following configurations are vulnerable: track_extra_parameters includes search_path (…
2025-11-09 - PgBouncer 1.25.0 - "The one with LDAP support" Features Add LDAP authentication! You can configure it using an HBA file or using auth_ldap_options. (#731) Add support for client-side direct TLS connections. This allows clients to using the faster TLS connection setup that was introduced in PostgreSQL 17. PgBouncer cannot (yet) connect to PostgreSQL servers using this faster connection…
2025-04-16 - PgBouncer 1.24.1 - "CVE-2025-2291 VALID UNTIL yesterday" Security Fix CVE-2025-2291: Previously PgBouncer did not take into account the VALID UNTIL of a user password when querying for password hashes using its auth_query. So if PgBouncer is used as a transparent proxy in front of Postgres it could allow passwords that had already expired. To solve this issue the default auth_query an…
2025-01-10 - PgBouncer 1.24.0 - "New year, new bouncer" Features Add support for Type=notify-reload for systemd. This requires systemd version 253 or later. (#1148) Add KILL_CLIENT command to the admin console. This allows terminating a client connection by force. (#1147) Add max_user_client_connections setting, both globally and at the user level. (#1137) Add max_db_client_connections setting, bo…
2024-08-02 - PgBouncer 1.23.1 - "Everything is put back in order" Fixes Fix a possible segmentation fault after PgBouncer reloads its configuration. (#1105) (bug introduced in 1.23.0) Fix all known put_in_order crashes. (#1120) (new crashes were introduced in 1.23.0) Add missing files to release tarball that are required for testing. (#1124) (missing files were introduced in 1.23.0) All changes: p…
No content.
2024-07-03 - PgBouncer 1.23.0 - "Into the new beginnings" Features Add support for rolling restarts. SIGTERM doesn't cause immediate shutdown of the PgBouncer process anymore. It now does a "super safe shutdown": waiting for all clients to disconnect before shutting down. The new SIGTERM behaviour allows rolling restarts of multiple PgBouncer processes behind a load balancer, or listening on the s…
2024-03-04 - PgBouncer 1.22.1 - "It's summer in Bangalore" Fixes Fix issues caused by some clients using COPY FROM STDIN queries. Such queries could introduce memory leaks, performance regressions and prepared statement misbehavior. ([#1025]) (bug introduced in 1.21.0) Add missing tests to release tarball ([#1026]) (missing tests were introduced in 1.19.0 & 1.21.0) All changes: pgbouncer_1_22_0...…
2024-01-31 - PgBouncer 1.22.0 - "DEALLOCATE ALL" Features Adds support for DEALLOCATE ALL and DISCARD ALL when max_prepared_statements is set to a non-zero value (normal DEALLOCATE is still unsupported) (#972) Support configuring auth_query per database (#979) Changes Improve settings in the recommended systemd unit file (#983) Make fail fast logic handle all scenarios where no working connections…