cve.bz

CVE-2026-107350 Improper Authentication

8.8 highEPSS 0.4%

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

On this page
Improper authentication in PgBouncer 1.17.0 through 1.26.0 allows a remote attacker who knows the password of a user listed in auth_file to log in as any other user that authenticates using SCRAM, including PgBouncer admin users and backend superusers. A second StartupMessage sent during SCRAM authentication against a non-existent database is not rejected and switches the user being logged in as, while the SCRAM exchange is still verified against the keys of the first user.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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; 31st 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: no · Technical impact: total, 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.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
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-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.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13pgbouncerno fix listedDEBIAN-CVE-2026-107350
Debian14pgbouncer1.26.1-1DEBIAN-CVE-2026-107350
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morepgbouncerno fix listedUBUNTU-CVE-2026-107350
Red Hathummingbird:1pgbouncer0:1.26.1-1.hum1RHSA-2026:83843
Azure Linux3pgbouncer1.26.1-1AZL-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

Red Hat rates this Important.

Red Hat's statement

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.

Red Hat's mitigation

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.

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-107350.

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

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

References

Check your stackJSON