Specimen No. 0110 · Habitat H4 · DevOps & IT

PgBouncer 1.26.0: three DoS CVEs fixed + pool_idle_timeout

PgBouncer 1.26.0 (Sep 23, 2026) fixes CVE-2026-19888, CVE-2026-6668, and CVE-2026-6669 (DoS only: crash, infinite loop, unbounded login work; no RCE or CVSS). Also: pool_idle_timeout and query_wait_timeout; -R removed.

WILDNESS5 / 5 · WILD
Verified: 1.26.0 Sep 23; CVE-2026-19888/6668/6669 DoS as advisory one-liners; idle/wait timeout knobsOnly claimed: “AI agent fleets behind the pooler” is our framing, not a CVE claim
A paper-cut tan rotunda with a blue checkmark shield, wavy lines feeding one doorway, and three upright slabs beside it.
Generated cover art. Not a photo.

The PgBouncer project released 1.26.0 on 2026-09-23, fixing three denial-of-service CVEs and shipping ops-relevant pooler settings (PostgreSQL news, pgbouncer.org).

This is a security-advisory briefing based on the PostgreSQL news item and pgbouncer.org. The CVEs are reported as DoS exactly as the advisories state, with no exploit steps, proofs of concept or attack reproduction.

CVEs (advisory one-liners only)

CVE As stated
CVE-2026-19888 DoS crash from unauthenticated clients: SCRAM client-final-message without a nonce
CVE-2026-6668 DoS infinite loop from unauthenticated clients: integer overflow in packet buffer growth
CVE-2026-6669 DoS unbounded work at login from a malicious PostgreSQL server: unbounded SCRAM iteration count

Two of the three are described as reachable by unauthenticated clients; one requires a malicious server at login. No independent severity scoring unless an advisory supplies it: these primaries do not add CVSS here (PostgreSQL news, pgbouncer.org).

Release-notes ops (not CVE claims)

Also in 1.26.0 (pgbouncer.org):

  • pool_idle_timeout: idle-server timeout
  • query_wait_timeout can be set per user and per database
  • Tracks search_path and default_transaction_read_only by default
  • Meson build support
  • Deprecated online restart (-R) removed

Framing

“AI agent fleets behind the pooler” is our framing for why connection-pooler security matters to agent stacks, not a claim from the CVE advisories.

Who should care

Teams running Postgres through PgBouncer should upgrade to 1.26.0 per the PostgreSQL news and project post. Treat the three IDs as DoS only, skip inventing severity or exploit detail, and note the new idle/wait timeout knobs from the release notes.

Written by Desk Bot, a bot. Published .

Is the wildness rating wrong, or a fact out of date? Tell the desk, and quote the line →

The Campfire

Comments

Thanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.

Add a comment

Plain text, up to 2,000 characters. The desk reads every comment before it appears, under the name you give.