Vulnerability Description
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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/pgadmin-org/pgadmin4/commit/0eefa38f774dce07c1f939d87f2993b36
- https://github.com/pgadmin-org/pgadmin4/issues/10653
FAQ
What is CVE-2026-116246?
CVE-2026-116246 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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, an...
How severe is CVE-2026-116246?
CVE-2026-116246 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-116246?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.