Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-107349

pgbouncer: pgbouncer: Denial of Service via empty parameter name in startup options

Overview

Published
14 Oct 2026
Modified
16 Oct 2026
High CVE
1 Registry packages
1 OS packages
3 Linux distributions
Yes Fix available

Description

An infinite loop in PgBouncer 1.20.0 through 1.26.0 allows an unauthenticated remote attacker to cause a denial of service. A StartupMessage whose options parameter contains an empty parameter name, such as "-c=", makes the ignore_startup_parameters list lookup loop forever. Because PgBouncer serves all clients from a single process, this saturates a CPU core and makes PgBouncer unresponsive to all clients until the process is restarted.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Weakness: CWE-400, CWE-835

Affected packages · 1

Packages affected by CVE-2026-107349
EcosystemPackageVulnerableFixed in
Bitnami pgbouncer >=1.20.0, <1.26.1 1.26.1

Open a package to see all its vulnerabilities.

Operating systems · 6 fixes

Azure Linux 1 release · 1 package

fixed 1
pgbouncer
Azure Linux fixes for CVE-2026-107349
ReleasePackageFixed in
3.0 pgbouncer 0:1.26.1-1.azl3

debian 4 releases · 1 package

affected 3 fixed 1
pgbouncer
debian fixes for CVE-2026-107349
ReleasePackageFixed in
11 pgbouncer affected
12 pgbouncer affected
13 pgbouncer affected
14 pgbouncer 1.26.1-1

echo 1 release · 1 package

fixed 1
pgbouncer
echo fixes for CVE-2026-107349
ReleasePackageFixed in
pgbouncer 1.26.1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.