CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HHigh (7.5). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExplain 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.
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | pgbouncer | no fix listed | DEBIAN-CVE-2026-107349 |
| Debian | 14 | pgbouncer | 1.26.1-1 | DEBIAN-CVE-2026-107349 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS and 4 more | pgbouncer | no fix listed | UBUNTU-CVE-2026-107349 |
| Red Hat | hummingbird:1 | pgbouncer | 0:1.26.1-1.hum1 | RHSA-2026:83843 |
| Azure Linux | 3 | pgbouncer | 1.26.1-1 | AZL-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 rates this Important.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | pgbouncer-main-1.26.1-1.hum1 | Fixed 2026-10-16 | RHSA-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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.