Schwachstellen / CVE-2026-17349

kritisch

CVE-2026-17349

pgadmin4: pgAdmin 4: Unauthorized database credential access via adhoc server cloning

Veröffentlicht Geändert CWE 522, 639
In der Trivy Database seit spätestens 24. Okt. 2026, 07:11 UTCWann der Eintrag vor diesem Build hinzukam, ist nicht erfasst.

Einstufung nach Quelle

Red Hat9.6CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Trivys eigenes Label ist CRITICAL. Kritisch laut Red Hat.

Beschreibung

/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.

Betroffene Pakete und behobene Versionen

QuellePaketBehoben in
rapidfort fedora 43pgadmin4, pgadmin4-doc, pgadmin4-httpd und 10 weitere9.18-1.fc43
Alle 13 Einträge aus 1 Quelle zeigen
QuellePaketBehoben in
rapidfort fedora 43pgadmin49.18-1.fc43
rapidfort fedora 43pgadmin4-doc9.18-1.fc43
rapidfort fedora 43pgadmin4-httpd9.18-1.fc43
rapidfort fedora 43pgadmin4-langpack-cs9.18-1.fc43
rapidfort fedora 43pgadmin4-langpack-de9.18-1.fc43
rapidfort fedora 43pgadmin4-langpack-es9.18-1.fc43
rapidfort fedora 43pgadmin4-langpack-fr9.18-1.fc43
rapidfort fedora 43pgadmin4-langpack-it9.18-1.fc43
rapidfort fedora 43pgadmin4-langpack-ja9.18-1.fc43
rapidfort fedora 43pgadmin4-langpack-ko9.18-1.fc43
rapidfort fedora 43pgadmin4-langpack-pl9.18-1.fc43
rapidfort fedora 43pgadmin4-langpack-ru9.18-1.fc43
rapidfort fedora 43pgadmin4-qt9.18-1.fc43

Referenzen

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.