CVE-2026-107349 json
Infinite loop on empty option name in startup options parameter in PgBouncer
published 26d ago modified 19d ago also BIT-pgbouncer-2026-107349 , EUVD-2026-101499
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami pgbouncer 1.26.1
- n/a PgBouncer 1.26.1
- pgbouncer Debian 14 1.26.1-1
debian advisories DEBIAN-CVE-2026-107349
- pgbouncer hummingbird 1 1.26.1-1.hum1
red hat advisories RHSA-2026:83843
- pgbouncer Azure Linux 3.0 1.26.1-1
azure linux advisories AZL-108192
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
Is CVE-2026-107349 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-107349 updated cvss 7.5
pgbouncer: pgbouncer: Denial of Service via empty parameter name in startup options
-
Red Hat Hardened Images pgbouncer 1.26.1-1.hum1fixed: vendor fix RHSA-2026:83843
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 24d ago
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | pgbouncer | >=1.20.0, <1.26.1 |
1.26.1 |
Affected products
- n/a PgBouncer
Classification
References
Sources
- CVE List CVE-2026-107349
- NVD CVE-2026-107349
- OSV BIT-pgbouncer-2026-107349
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.