CVE-2026-107350

Отчет

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.