cve.bz

CVE-2026-107349 Uncontrolled Resource Consumption

7.5 highEPSS 0.4%

High (7.5). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-107349 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107349?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107349?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107349 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13pgbouncerno fix listedDEBIAN-CVE-2026-107349
Debian14pgbouncer1.26.1-1DEBIAN-CVE-2026-107349
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morepgbouncerno fix listedUBUNTU-CVE-2026-107349
Red Hathummingbird:1pgbouncer0:1.26.1-1.hum1RHSA-2026:83843
Azure Linux3pgbouncer1.26.1-1AZL-108192

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because PgBouncer can be rendered entirely unavailable by an unauthenticated remote client without requiring special privileges or prior authentication. Because PgBouncer serves pooled connections through a single process architecture, the resulting infinite loop monopolizes execution and prevents processing of any database traffic. The entire connection pool remains completely unresponsive until the daemon is manually restarted by an administrator.

Red Hat's mitigation

Restrict network access to the PgBouncer service so that only trusted application hosts and administrative clients can connect. This can be accomplished by configuring firewall filtering using firewalld or by binding PgBouncer only to internal, isolated interfaces.

For example, to restrict access to PgBouncer (default port 6432/TCP) to a trusted subnet (such as 192.168.1.0/24):

1. Add a rich rule allowing only the trusted source subnet:

# firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="6432" protocol="tcp" accept'

2. Ensure the port is not exposed in public zones:

# firewall-cmd --permanent --remove-port=6432/tcp

3. Reload firewalld to apply changes:

# firewall-cmd --reload

Caveats: Network-level restrictions reduce exposure to untrusted external clients but do not mitigate risks originating from compromised or untrusted hosts within the allowed network. Modifying firewall rules or listener configurations can momentarily disrupt active client sessions and connection pooling.

ProductPackageStateAdvisory
Red Hat Hardened Imagespgbouncer-main-1.26.1-1.hum1Fixed 2026-10-16RHSA-2026:83843

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-107349.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON