CVE-2026-17349
Received Received - Intake

Privilege Escalation in pgAdmin 4 Workspaces Feature

Vulnerability report for CVE-2026-17349, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-31

Last updated on: 2026-07-31

Assigner: PostgreSQL

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-31
Last Modified
2026-07-31
Generated
2026-07-31
AI Q&A
2026-07-31
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
pgadmin pgadmin to 9.17 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
CWE-522 The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in pgAdmin 4 (versions 9.0 to 9.16) involves improper handling of server cloning in the adhoc_connect_server component. When a non-owner triggers an adhoc connection to another user's shared server, the system incorrectly clones the server with the original user's ownership, sharing settings, and stored database credentials. This allows the non-owner to inherit and use the original user's credentials without authorization.

Detection Guidance

This vulnerability affects pgAdmin 4 versions 9.0 to 9.16. To detect it, check if any non-owner users have cloned servers with inherited credentials from administrators or other users. Review server ownership and credential fields in the pgAdmin database for unauthorized modifications.

Impact Analysis

If you are a pgAdmin user, an attacker with access to your instance could exploit this to gain unauthorized access to databases using credentials they should not have. This could lead to data breaches, unauthorized data manipulation, or privilege escalation within the database system.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating compliance requirements such as GDPR (data protection) and HIPAA (health information privacy). It may result in data breaches, unauthorized disclosures, and failure to maintain proper access controls, leading to legal and regulatory penalties.

Mitigation Strategies

Upgrade pgAdmin 4 to version 9.17 or later to apply the fix. If upgrading is not immediately possible, restrict adhoc connect functionality or audit server ownership and credentials manually to ensure no unauthorized access persists.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-17349. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart