Is CVE-2026-107349 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-107349 being exploited in the wild.

How severe is CVE-2026-107349?

High severity, with a CVSS score of 7.5, published 14 October 2026.

Which products and versions are affected?

PgBouncer 1.20.0 through 1.26.0.

Is there a fix for CVE-2026-107349?

Yes: fixed in PgBouncer 1.26.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-107349 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-107349?

Check whether you run PgBouncer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-107349: PgBouncer infinite loop denial of service in startup message parsing

CVE-2026-107349 · Severity: high · CVSS 7.5 · Published 2026-10-14

PgBouncer is a connection pooler for PostgreSQL databases that routes client connections to backend servers. An unauthenticated attacker can send a specially crafted network message to cause PgBouncer to enter an infinite loop, consuming a CPU core and making the service unresponsive to all clients until it is manually restarted.

Technologies: PgBouncer. Vendors: PgBouncer.

Quick answers

Is CVE-2026-107349 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-107349 being exploited in the wild.
How severe is CVE-2026-107349?: High severity, with a CVSS score of 7.5, published 14 October 2026.
Which products and versions are affected?: PgBouncer 1.20.0 through 1.26.0.
Is there a fix for CVE-2026-107349?: Yes: fixed in PgBouncer 1.26.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-107349 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-107349?: Check whether you run PgBouncer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: PgBouncer 1.26.1

Technical details

An infinite loop occurs in the ignore_startup_parameters list lookup when processing a PostgreSQL StartupMessage with an empty parameter name (e.g., "-c="). Since PgBouncer uses a single process to serve all clients, the CPU-bound loop saturates a core and halts all client operations. The vulnerability requires that ignore_startup_parameters be non-empty but not contain the specific option being processed; it is triggered pre-authentication via the network.

Affected products

pgbouncer PgBouncer 1.20.0 through 1.26.0

Timeline

2026-10-14: disclosed
2026-10-14: patched: PgBouncer 1.26.1 released

References

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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.