pgAdmin 4: Server passwords are left in pgAdmin's process environment

Özet

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

To pass a server's password to psql and to the utilities pgAdmin 4 runs as background processes, the server manager wrote it into pgAdmin's own process environment: as PGPASSWORD for the PSQL tool, and under a per-process variable for a utility. Nothing removed it afterwards. pgAdmin's environment is shared by every user's requests and copied into every process it starts, so in server mode another user's later PSQL session or utility inherited the password, and libpq used PGPASSWORD for any connection made without a password of its own, letting one user connect with another user's saved password.

The fix puts the password only into the environment built for the process that needs it and starts psql with a copy of pgAdmin's environment instead of the environment itself.

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/0eefa38f774dce07c1f939d87f2993b36e2313b9 Yama
• github.com/pgadmin-org/pgadmin4/issues/10653 Üçü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
• 8,2 CVE-2026-116247pgAdmin 4: libpq uses the pgAdmin service account's own password file and client certificate