CVE-2026-116246: high-severity vulnerability in pgadmin.org pgAdmin 4
pgAdmin 4: Server passwords are left in pgAdmin's process environment
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7epss 0.2%
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:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:L/SA:N
Affected products
pgadmin.org · pgAdmin 4Related CVEs — pgadmin.org pgAdmin 4
In the same product, most dangerous first.
CVE-2024-2044CRITICALUnsafe Deserialisation and Remote Code Execution by an Authenticated user in pgAdmin 4EPSS 79.5%CVE-2024-3116HIGHRemote Code Execution Vulnerability through the validate binary path API in pgAdmin 4EPSS 65.8%CVE-2025-2945CRITICALpgAdmin 4: Remote Code Execution in Query Tool and Cloud DeploymentEPSS 56.3%CVE-2025-12762CRITICALRemote Code Execution vulnerability when restoring PLAIN-format SQL dumps in server mode (pgAdmin 4)EPSS 12.7%CVE-2024-9014CRITICALOAuth2 client id and secret exposed through the web browser in pgAdmin 4EPSS 9.7%CVE-2026-7816HIGHpgAdmin 4: OS command injection in Import/Export query export via psql metacommand breakoutEPSS 1.4%