CVE-2026-116243

pgAdmin 4 runs pgdump, pgrestore, pgdumpall and psql from the binary path a user sets in their preferences. In server mode the binary path was refused only when it lay under the per-user storage directory STORAGEDIR, not under a SHAREDSTORAGE directory, which ordinary users can upload files to. A...

CVE-2026-116248

In pgAdmin 4 server mode only administrators are meant to share a server with all users; the server dialog shows the Shared switch only to them. The create and update endpoints of the server API, however, stored the "shared" flag and shared username they were sent, so any user able to register a...

CVE-2026-116239

In server mode pgAdmin 4 keeps an account per authentication source, so the same username can exist as, for example, an internal account and an LDAP account. After LDAP or Kerberos authenticated a user, pgAdmin chose the account to log in by username alone, or took the account Flask-Security's...

CVE-2026-116238

In server mode pgAdmin 4 locks an internal account after MAXLOGINATTEMPTS failed logins 3 by default. The limit could be bypassed, giving an unauthenticated attacker an unlimited number of password guesses against any internal account, including the administrator's, in the default configuration: ...

CVE-2026-116250

This vulnerability affects pgAdmin 4 versions prior to 9.19 when running in server mode. The application performs a path validation check using check_access_permission() but subsequently opens the file by name using open(). A TOCTOU (Time-of-Check Time-of-Use) race condition allows an attacker to...

CVE-2026-116249

In pgAdmin 4 versions before 9.19 , a vulnerability exists where the application fails to properly sanitize file paths relative to the user's storage directory. Because get_complete_file_path() only strips leading slashes, an attacker can use path traversal sequences (e.g., ..//.pgpass) via the s...

CVE-2026-116249 pgAdmin 4: Connection file paths and parameter keys escape the user's storage directory

In server mode pgAdmin 4 resolves a server's password file, SSL certificate, key, CRL and SSH tunnel identity file relative to the user's storage directory, but getcompletefilepath only stripped leading slashes before joining the two. A path such as "..//.pgpass", set through the server dialog, t...

CVE-2026-116250 pgAdmin 4: Files opened in a storage directory follow a symbolic link, hard link or FIFO planted after the containment check

In server mode pgAdmin 4 validates a path a user gives for a file in their storage directory with checkaccesspermission and then opened it by name. Several places opened it with a plain open or handed the path to a utility that opened it later: the servers.json export and import and the import fi...

EUVD-2026-114389

In pgAdmin 4 server mode only administrators are meant to share a server with all users; the server dialog shows the Shared switch only to them. The create and update endpoints of the server API, however, stored the "shared" flag and shared username they were sent, so any user able to register a...

EUVD-2026-114388

When a server in pgAdmin 4 had no password file, client certificate or client key configured, or the configured one could not be found, pgAdmin left the parameter out of the connection and libpq fell back to the defaults of the operating-system account running pgAdmin: /.pgpass,...

CVE-2026-116247 pgAdmin 4: libpq uses the pgAdmin service account's own password file and client certificate

When a server in pgAdmin 4 had no password file, client certificate or client key configured, or the configured one could not be found, pgAdmin left the parameter out of the connection and libpq fell back to the defaults of the operating-system account running pgAdmin: /.pgpass,...

EUVD-2026-114386

libpq looks a connection service up in the service file of the operating-system account running pgAdmin 4, and an entry there can hold a password or name a password file or client certificate. In server mode any user could set a server's Service, or a "service" connection parameter, to one of tho...

CVE-2026-116245

This vulnerability affects pgAdmin 4 versions before 9.19 . In server mode, the application fails to restrict connection services, allowing any user to set a server's Service or service connection parameter to an entry in the operating-system account's service file. Because these entries can cont...

CVE-2026-116245 pgAdmin 4: Connection services are not restricted in server mode

libpq looks a connection service up in the service file of the operating-system account running pgAdmin 4, and an entry there can hold a password or name a password file or client certificate. In server mode any user could set a server's Service, or a "service" connection parameter, to one of tho...

CVE-2026-116243

In pgAdmin 4 versions before 9.19, a vulnerability exists where the application failed to block utility binary paths (for pg_dump, pg_restore, pg_dumpall, and psql) pointing to a SHARED_STORAGE directory. Because ordinary users can upload files to shared storage, an attacker could upload an execu...

EUVD-2026-114384

pgAdmin 4 runs pgdump, pgrestore, pgdumpall and psql from the binary path a user sets in their preferences. In server mode the binary path was refused only when it lay under the per-user storage directory STORAGEDIR, not under a SHAREDSTORAGE directory, which ordinary users can upload files to. A...

CVE-2026-116242

The software pgAdmin 4 (versions prior to 9.19 ) is vulnerable to a security flaw when opening SSH tunnels using the sshtunnel library. Because the application fails to specify the host_pkey_directories or ssh_config_file, it defaults to loading unencrypted private keys from the ~/.ssh directory ...

CVE-2026-116242 pgAdmin 4: SSH tunnels use the pgAdmin service account's own SSH identity

pgAdmin 4 opens SSH tunnels with the sshtunnel library but gave it neither hostpkeydirectories nor sshconfigfile, 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...

EUVD-2026-114380

In server mode pgAdmin 4 keeps an account per authentication source, so the same username can exist as, for example, an internal account and an LDAP account. After LDAP or Kerberos authenticated a user, pgAdmin chose the account to log in by username alone, or took the account Flask-Security's...

CVE-2026-116240

In server mode, pgAdmin 4 (versions before 9.19 ) is vulnerable to path traversal and TOCTOU issues due to inconsistent path handling in check_access_permission(). The system validates one path but subsequently acts on a differently constructed path. Specifically, stripping slashes can allow acce...