CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (8.8). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-107350 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107350?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107350?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-107350 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-107350 |
| Debian | 14 | pgbouncer | 1.26.1-1 | DEBIAN-CVE-2026-107350 |
| Ubuntu | 16.04:LTS, 18.04:LTS, 20.04:LTS and 4 more | pgbouncer | no fix listed | UBUNTU-CVE-2026-107350 |
| Red Hat | hummingbird:1 | pgbouncer | 0:1.26.1-1.hum1 | RHSA-2026:83843 |
| Azure Linux | 3 | pgbouncer | 1.26.1-1 | AZL-108189 |
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.
Red Hat has evaluated this vulnerability as Important severity because an authenticated remote user with valid credentials can gain unauthorized administrative privileges over the database tier, potentially compromising data confidentiality and integrity across all managed databases. Although exploitation requires legitimate credentials for at least one account, the ability to jump from low-privilege client access to backend superuser status represents a substantial escalation beyond expected authorization boundaries. In typical Red Hat environments where PgBouncer pools connections for external applications, exposing the pooler to multiple untrusted or semi-trusted tenants elevates the risk of complete infrastructure takeover.
Limit network access to the PgBouncer daemon so that only trusted application hosts can establish connections.
1. Using firewalld, restrict traffic on the PgBouncer port (default 6432/tcp) to specific authorized client IP addresses:
# firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_CLIENT_IP>
# firewall-cmd --permanent --zone=trusted --add-port=6432/tcp
# firewall-cmd --permanent --remove-port=6432/tcp --zone=public
# firewall-cmd --reload
Alternatively, if clients reside on the same host, bind PgBouncer exclusively to the loopback interface by configuring `listen_addr = 127.0.0.1` in `/etc/pgbouncer/pgbouncer.ini` and applying changes:
# systemctl reload pgbouncer
Caveats: Restricting network reachability prevents untrusted network hosts from connecting, but it does not protect against malicious or compromised clients residing within the permitted network range. Modifying firewall rules or reloading the PgBouncer service may briefly disrupt active client connections.
| 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-107350.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.