CVE-2026-17349: pgAdmin 4: Adhoc server clone leaks another user's stored database credentials and ownership to a non-owner
/misc/workspace/adhocconnectserver, 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 userid, shared, sharedusername, and the stored credential fields password, savepassword, and tunnelpassword. 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 (userid, shared, sharedusername) and stored credential fields (password, savepassword, tunnelpassword) 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pgAdmin 4to a version that resolves this vulnerability.Fixed in 9.17 - Configuration
For Adhoc Connect server clones created via Server.clone(), force the cloned adhoc record's ownership fields (user_id, shared, shared_username) to belong to the calling user and force stored credential fields (password, save_password, tunnel_password) to be cleared/private before the clone row is committed, regardless of the source server's ownership, sharing state, or stored credentials.
pgAdmin 4 Adhoc Connect server clone (Server.clone/adhoc connect) ownership fields and stored credential fields on cloned record = Set user_id, shared, shared_username, password, save_password, and tunnel_password to calling user values (ownership) and clear/private the stored credentials before committing
Event History
Frequently Asked Questions
What is the severity of CVE-2026-17349?
The severity of CVE-2026-17349 is critical, with a score of 9.6.
What does CVE-2026-17349 affect?
CVE-2026-17349 affects pgAdmin 4, specifically the Workspaces feature introduced in version 9.0.
How do I fix CVE-2026-17349?
To fix CVE-2026-17349, upgrade pgAdmin 4 to the latest version that addresses this vulnerability.
What is the main issue with CVE-2026-17349?
The main issue of CVE-2026-17349 is that it leaks stored database credentials and ownership to a non-owner when cloning servers.
What is the impact of CVE-2026-17349?
The impact of CVE-2026-17349 includes unauthorized access to another user's database credentials and sensitive information.