Approved changes feed: RSS · Atom
cpe:2.3:a:n/a:pgbouncer:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | N/A (22f567d3-1203-528c-8f0e-3eb9c2f6ca78) |
|---|---|
| Product | Pgbouncer (c2cef5f0-12a2-5fc7-96d5-e5615ff6b3db) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-107350 |
vulnerable | 2026-11-03 10:15:59.500735 |
Authentication bypass via second StartupMessage during SCRAM authentication in PgBouncer
HIGH (8.8)
Improper authentication in PgBouncer 1.17.0 through 1.26.0 allows a remote attacker who knows the password of a user listed in auth_file to log in as any other user that authenticates using SCRAM, including PgBouncer admin users and backend superusers. A second StartupMessage sent during SCRAM authentication against a non-existent database is not rejected and switches the user being logged in as, while the SCRAM exchange is still verified against the keys of the first user.
Published: 2026-10-14T17:34:39.009Z
Updated: 2026-10-16T14:18:50.053Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6667 |
vulnerable | 2026-06-08 08:07:04.984483 |
PgBouncer missing authorization check in KILL_CLIENT admin command
MEDIUM (4.3)
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.
Published: 2026-05-09T00:43:53.126Z
Updated: 2026-05-11T14:44:43.075Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6666 |
vulnerable | 2026-06-08 08:07:04.984139 |
PgBouncer crash in kill_pool_logins_server_error
MEDIUM (5.9)
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.
Published: 2026-05-09T00:43:49.952Z
Updated: 2026-05-11T14:44:15.596Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6665 |
vulnerable | 2026-06-08 08:07:04.983799 |
PgBouncer buffer overflow in SCRAM
HIGH (8.1)
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.
Published: 2026-05-09T00:43:46.762Z
Updated: 2026-05-12T03:55:19.823Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6664 |
vulnerable | 2026-06-08 08:07:04.982041 |
PgBouncer integer overflow in PgBouncer network packet parsing
HIGH (7.5)
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.
Published: 2026-05-09T00:43:42.640Z
Updated: 2026-05-11T14:28:49.277Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-2291 |
vulnerable | 2026-06-08 07:16:56.739134 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-12819 |
vulnerable | 2026-06-08 07:04:31.033101 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-3935 |
vulnerable | 2026-06-08 05:33:54.597452 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.