Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
Set max_packet_size well below 1073741824 so that no single packet can grow a packet buffer past the overflow threshold
| Link | Providers |
|---|---|
| https://www.pgbouncer.org/changelog.html |
|
Wed, 23 Sep 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 23 Sep 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Integer overflow in the packet buffer growth logic in PgBouncer through 1.25.2 allows an unauthenticated remote attacker to cause a denial of service. Sufficiently large input makes the buffer size computation overflow, leaving the growth loop unable to terminate. Because PgBouncer serves all clients from a single process, this saturates a CPU core and stalls every pooled connection until the process is killed. Both unauthenticated and authenticated code paths can reach the overflow. | |
| Title | Integer overflow causes an infinite loop in packet buffer growth in PgBouncer | |
| Weaknesses | CWE-190 CWE-835 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-09-23T16:46:13.834Z
Reserved: 2026-04-20T12:25:46.351Z
Link: CVE-2026-6668
Updated: 2026-09-23T16:36:55.619Z
Status : Received
Published: 2026-09-23T17:17:16.073
Modified: 2026-09-23T17:17:16.073
Link: CVE-2026-6668
No data.
OpenCVE Enrichment
No data.