dbcve.org
Pgadmin 4Application · Pgadmin

CVE-2026-17349

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-31
Fix available
A fix is available. Upgrade to 9.17 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 3 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
/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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In pgAdmin 4 versions 9.0 through 9.16, the /misc/workspace/adhoc_connect_server endpoint uses Server.clone() which copies all columns including user_id, shared flag, and stored credentials (password, save_password, tunnel_password). When a non-owner triggers an adhoc connect against another user's shared server, the cloned row inherits the original owner's credentials while being owned by the attacker, allowing unauthorized database access using stolen credentials.

MitigationUpgrade pgAdmin 4 to version 9.17 or later, which forces cloned adhoc records to use the caller's ownership and clears stored credentials before persisting.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pgadmin 4Application
Affected:>= 9.0, < 9.17

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify pgAdmin 4 version
    Check the installed pgAdmin 4 version by querying the application. This can be done via the pgAdmin UI (Help > About), the Python package (pip show pgadmin4), or the server's package manager. Compare the version number to the affected range 9.0-9.16.
    Affected if The installed version is 9.0 through 9.16 inclusive.
  2. Confirm Workspaces feature is in use
    Verify that the Workspaces feature is enabled and that server sharing between users is configured. Check pgAdmin settings or logs for workspace-related operations and server sharing activity.
    Affected if Workspaces and server sharing are enabled, allowing users to share server configurations with other users.
  3. Audit server records for ownership anomalies
    Query the pgAdmin database for server configuration records where the user_id does not match the expected owner, particularly records created through adhoc connections. Look for entries where the shared flag is set but ownership points to a different user than the creator.
    Affected if Server records exist with mismatched ownership or where a non-owner user's workspace contains server configurations originally created by another user with persisted credentials.

A defender is affected if pgAdmin 4 version is 9.0-9.16, the Workspaces feature is active, and server records exist that show cross-user credential inheritance without proper ownership transfer.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.17 or later
Fixed in 9.17
Interim mitigation

Upgrade pgAdmin 4 to version 9.17 or later, which forces cloned adhoc records to use the caller's ownership and clears stored credentials before persisting.

Recommended fix High confidence

pgAdmin 4 version 9.17

  1. 1. Backup your current pgAdmin 4 configuration and database
  2. 2. Stop the pgAdmin 4 server if running
  3. 3. If using pip: run 'pip install --upgrade pgadmin4==9.17'
  4. 4. If using the standalone installer: download and install pgAdmin 4 version 9.17 or later from https://www.pgadmin.org/download/
  5. 5. Verify the installation by checking the version: import pgadmin; print(pgadmin.__version__)
  6. 6. Start the pgAdmin 4 server and test that the application functions normally
  7. 7. Test that the adhoc connect feature works as expected for your user context

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pgadmin 4 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-17349 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-17349 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data