Live › vulnerability › CVE-2026-116246
pgAdmin 4 wrote a server's saved password into its shared process environment and never removed it, so later sessions and tools could inherit it. In server mode, one user can connect to a database using another user's saved password.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 20:25 UTC. All times on this page are UTC.
Teams running pgAdmin 4 in server mode, where several users share one instance and use saved database passwords. Desktop-only use with a single user is less exposed. Versions before 9.19 are affected per the sources.
No product ranges from the sources yet.
9.19 are affected.9.19 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-116246")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.