# CVE-2026-17349: pgAdmin 4: Adhoc server clone leaks another user's stored database credentials and ownership to a non-owner > A non-owner can clone a shared server, inheriting the owner's database credentials and ownership, allowing unauthorized access to the database. - **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 31 Jul 2026 - **Updated:** 1 Aug 2026 - **Also known as:** GHSA-p547-rjmg-jqr4 ## What is CVE-2026-17349? CVE-2026-17349 is a critical missing authorization vulnerability in pgadmin.org pgAdmin 4, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-522 (Insufficiently Protected Credentials) ## Which versions are affected by CVE-2026-17349? It affects 1 product. Products: Pgadmin Pgadmin 4. ## How do I fix CVE-2026-17349? Upgrade to a fixed version. ## Is CVE-2026-17349 being exploited? There is no known exploitation of CVE-2026-17349 in the wild and no public exploit code. ## Other vulnerabilities in pgadmin.org pgAdmin 4 - [CVE-2025-2945](https://insights.sbomify.com/CVE-2025-2945/): pgAdmin 4: Remote Code Execution in Query Tool and Cloud Deployment (critical 9.9) - [CVE-2024-9014](https://insights.sbomify.com/CVE-2024-9014/): OAuth2 client id and secret exposed through the web browser in pgAdmin 4 (critical 9.9) - [CVE-2026-12046](https://insights.sbomify.com/CVE-2026-12046/): Deserialization in pgAdmin 4 (critical 9.5) - [CVE-2026-17351](https://insights.sbomify.com/CVE-2026-17351/): SQL injection in pgAdmin 4 (critical 9.4) - [CVE-2026-17566](https://insights.sbomify.com/CVE-2026-17566/): Command injection in pgAdmin 4 (critical 9.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-17349 and fix it if it is affected. What it is: CVE-2026-17349 is a critical missing authorization vulnerability in pgadmin.org pgAdmin 4, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-17349 in the wild and no public exploit code. Affected product: pgadmin.org pgAdmin 4. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-17349/ (Markdown: https://insights.sbomify.com/CVE-2026-17349/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-17349 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-17349 - OSV: https://osv.dev/vulnerability/CVE-2026-17349 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-17349/ Summaries are generated and may contain mistakes; the official description above is the record.