Service interruption via unbounded SCRAM iteration count
Published Sep 23, 2026 · Updated Sep 23, 2026
Denial of service in PgBouncer 1.25.2 and earlier allows malicious PostgreSQL backends to halt pooled traffic during SCRAM login. Its SCRAM client accepts a backend-supplied iteration count without an upper bound and performs the requested key-derivation work synchronously. Control of a configured backend is required; one crafted authentication exchange can monopolize the single process and stop service for every pooled database and client.
Summary
What happened
Denial of service in PgBouncer 1.25.2 and earlier allows malicious PostgreSQL backends to halt pooled traffic during SCRAM login. Its SCRAM client accepts a backend-supplied iteration count without an upper bound and performs the requested key-derivation work synchronously. Control of a configured backend is required; one crafted authentication exchange can monopolize the single process and stop service for every pooled database and client.
The record
- CVE
- CVE-2026-6669
- Published
- Sep 23, 2026
- Updated
- Sep 23, 2026
- Vendor
- PgBouncer
- Product
- PgBouncer
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2026CVE publishedPublication date reported by the CVE source.
- Sep 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.25.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started