CVE-2026-17349 Details
Description
/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.
A vulnerability exists in pgAdmin 4 versions 9.0 prior to 9.17 within the Workspaces feature. The issue arises in the 'adhoc_connect_server' function, where cloning a server inadvertently transfers ownership and sensitive database credentials from one user to another. This occurs when a non-owner connects to a shared server, as the cloned server retains the original owner's credentials, including database passwords and SSH tunnel passwords. Consequently, the non-owner can access the database using these inherited credentials, which were not rightfully theirs. The vulnerability persists even if the connection attempt fails, as the cloned server record is saved before the connection is established. The flaw allows for cross-tenant credential leakage, particularly involving shared servers owned by administrators.
Users can update to pgAdmin 4 version 9.17, where this vulnerability has been fixed. Instructions for updating can be found in the pgAdmin 4 release notes for version 9.17.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 31, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/pgadmin-org/pgadmin4/commit/64a9cdbd6a240a962144f84418beaf9e66419779 | PostgreSQL | Patch |
| https://github.com/pgadmin-org/pgadmin4/commit/a7e74a6ed685bc34e1f77a8b6a94d00fa3dff815 | PostgreSQL | Patch |
| https://github.com/pgadmin-org/pgadmin4/issues/10200 | PostgreSQL | Issue TrackingPatchVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-522 | Insufficiently Protected Credentials | PostgreSQL |
| CWE-639 | Authorization Bypass Through User-Controlled Key | PostgreSQL |
Affected Products
| Product | Versions |
|---|---|
| pgadmin pgadmin 4 | >= 9.0, < 9.17 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 23, 2026 | CVE Translated | [email protected] |
| Aug 5, 2026 | Initial Analysis | [email protected] |
| Aug 1, 2026 | CVE Modified | CISA-ADP |
| Jul 31, 2026 | CVE Modified | CISA-ADP |
| Jul 31, 2026 | New CVE Received | PostgreSQL |