Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
8.6
CVE-2026-17349: pgAdmin 4 lets non‑owner see another user’s database passwords
CVE-2026-17349 · published 3 months ago
Summary
A feature in pgAdmin 4 that copies a server configuration can also copy the original owner's saved login details. If a different user triggers this copy, they receive the other person's database password and can connect using those privileges. Upgrade pgAdmin to the latest release where the copy is cleared of another user’s credentials.
What to do
- Update pgadmin.org pgadmin 4 to version 9.17 or later.
- Update pgadmin pgadmin_4 to version 9.17 or later.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| pgadmin.org | pgadmin 4 | < 9.17 |
| pgadmin | pgadmin_4 |
>= 9.0, < 9.17 cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:postgresql:*:* |
Original advisory text
pgAdmin 4: Adhoc server clone leaks another user's stored database credentials and ownership to a non-owner
/misc/workspace/adhoc_connect_server, part of the Workspaces feature introduced in pgAdmin 4 9.0, when passed the id of an existing server, clones that server via Server.clone(), which copies every column from the source row, including user_id, shared, shared_username, and the stored credential fields password, save_password, and tunnel_password. When a non-owner triggered an adhoc connect against another user's (in practice, typically an administrator's) shared server, the clone inherited that user's ownership, shared flag, and stored database credentials verbatim. pgAdmin persisted this cross-tenant, credential-bearing server row before the connection was even attempted, so it survived even when the connection subsequently failed. The non-owner could then open the newly-owned clone and pgAdmin would connect using the source user's stored database password on the non-owner's behalf, granting the non-owner use of database credentials -- and whatever database privileges they confer -- that were never their own.
Fix forces the cloned adhoc record's ownership fields (user_id, shared, shared_username) and stored credential fields (password, save_password, tunnel_password) to belong to the calling user and be cleared/private before committing, regardless of the source server's ownership, sharing state, or stored credentials. A regression test asserts that an adhoc connect triggered by a non-owner against another user's shared server persists a row owned by the caller, not shared, and without the source's stored credentials.
This issue affects pgAdmin 4: from 9.0 before 9.17.
Fix forces the cloned adhoc record's ownership fields (user_id, shared, shared_username) and stored credential fields (password, save_password, tunnel_password) to belong to the calling user and be cleared/private before committing, regardless of the source server's ownership, sharing state, or stored credentials. A regression test asserts that an adhoc connect triggered by a non-owner against another user's shared server persists a row owned by the caller, not shared, and without the source's stored credentials.
This issue affects pgAdmin 4: from 9.0 before 9.17.
References
- https://github.com/pgadmin-org/pgadmin4/issues/10200 Third Party Advisory
- https://github.com/pgadmin-org/pgadmin4/commit/64a9cdbd6a240a962144f84418beaf9e6... Patch
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/17xxx/CVE-2026-17349... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-17349 Vendor Advisory
- https://github.com/pgadmin-org/pgadmin4/commit/a7e74a6ed685bc34e1f77a8b6a94d00fa... Patch
- https://github.com/pgadmin-org/pgadmin4 Product
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker full control
Severity
8.6
High
Type
CWE-522Insufficiently Protected Credentials
CWE-639Authorization Bypass Through User-Controlled Key
Timeline
Published31 Jul 2026
Updated12 Nov 2026
First seen31 Jul 2026
Track software like this
Free during beta