CVE-2026-6669

published 23 Sep 2026 · updated 7 Oct 2026

Unbounded SCRAM iteration count causes CPU exhaustion in PgBouncer

5.9MediumCVSS 5.9EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
<=1.25.2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-6669 severity on Zeptric[![CVE-2026-6669](https://zeptric.io/badge/cve/CVE-2026-6669.svg)](https://zeptric.io/cve/CVE-2026-6669)