pgAdmin 4: SSH tunnels use the pgAdmin service account's own SSH identity

Özet

Türkçe özeti henüz hazır değil; şimdilik kaynağın kendi açıklamasını gösteriyoruz.

pgAdmin 4 opens SSH tunnels with the sshtunnel library but gave it neither host_pkey_directories nor ssh_config_file, so it always loaded the unencrypted private keys in ~/.ssh of the operating-system account running pgAdmin, read that account's ~/.ssh/config (IdentityFile, User, HostName, ProxyCommand) for the tunnel host, and could use its ssh-agent. In server mode any user could therefore configure a tunnel to a host that accepts the service account's key, with no credentials of their own or with an identity file that did not exist in their storage, and reach it as that account.

The fix makes tunnels in server mode use only the identity file or password the user configured: the service account's keys, configuration and agent are no longer used, and an identity file that cannot be found in the user's storage is reported instead of falling back to ~/.ssh. Desktop mode is unchanged.

This issue affects pgAdmin 4: before 9.19.

Etkilenen sürümler1 yazılım

Kaynaklar4 kaynak

• CVE.org kaydı
• NVD kaydı
• github.com/…ommit/d52fe4740eb1af89d940f2e412bd66a0a89f08bb Yama
• github.com/pgadmin-org/pgadmin4/issues/10662 Üçüncü taraf

Kayıt geçmişi

1. 30 Eki 2026 22:55Yayımlandı

İlgili açıklar

• 6,5 CVE-2026-116252pgAdmin 4: Materialized view refresh redirects its connection through a crafted database name
• 4,2 CVE-2026-116251pgAdmin 4: A user's other sessions survive a change of their password
• 8,4 CVE-2026-116249pgAdmin 4: Connection file paths and parameter keys escape the user's storage directory
• 6,5 CVE-2026-116250pgAdmin 4: Files opened in a storage directory follow a symbolic link, hard link or FIFO planted after the containment check
• 6,8 CVE-2026-116248pgAdmin 4: Non-administrators can share a server with every user
• 6,5 CVE-2026-116246pgAdmin 4: Server passwords are left in pgAdmin's process environment