Resource exhaustion in Pgbouncer
CVE-2026-6669
Missing upper bound on the key derivation iteration count accepted during SCRAM authentication to a backend server in PgBouncer through 1.25.2 allows a malicious or compromised PostgreSQL backend to cause uncontrolled CPU consumption in PgBouncer. The resulting key derivation cannot be interrupted in frontend builds such as PgBouncer. Because PgBouncer serves all clients from a single process, one backend can in this way stop it from serving traffic for every other database and client it is pooling, so the failure of a single backend is not contained.
Vulnerability class: DoS (Denial of Service)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Pgbouncer
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-6669?
- CVE-2026-6669 is a medium-severity vulnerability in Pgbouncer, classified under Uncontrolled Resource Consumption. CVSS score: 5.9/10. Published 2026-09-23.
- How severe is CVE-2026-6669?
- Medium severity. CVSS v3 base score is 5.9 out of 10.