Read the docs

Path traversal in pgAdmin 4 lets users reach other users' files

Priority LOW 33CWE-22Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
High · Low · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

In server mode, pgAdmin 4 before 9.19 resolves the password file, SSL certificate, key, CRL and SSH identity file paths of a server relative to the user's storage directory, but it only strips leading slashes, so parent directory references (CWE-22) let a path name another user's files. An authenticated user with low privileges who can set these paths through the server dialog, the REST API or a servers.json import can connect with another user's saved passwords, client certificate or SSH key. The sslkeylogfile parameter was also not confined, so it could make pgAdmin's account create or append files outside storage.

Written with Claude Haiku 5.5 from the sources below · 2026-11-05

Description from the CNA

In server mode pgAdmin 4 resolves a server's password file, SSL certificate, key, CRL and SSH tunnel identity file relative to the user's storage directory, but get_complete_file_path() only stripped leading slashes before joining the two. A path such as "../<another user>/.pgpass", set through the server dialog, the REST API or a servers.json import, therefore named another user's file, and connecting used that user's saved passwords, client certificate or SSH key. The sslkeylogfile connection parameter was passed to libpq unchanged, so a path outside storage let libpq create or append a file as the account running pgAdmin. make_conninfo() also quoted connection parameter values but not their names, so a crafted parameter name could smuggle additional keyword=value pairs past these checks. The fix requires the resolved path, with symbolic links followed, to stay inside the user's storage directory or the named shared storage directory, confines sslkeylogfile the same way, and accepts only exact libpq keywords as connection parameter names. A refused path or keyword is reported instead of letting libpq fall back to a default. This issue affects pgAdmin 4: before 9.19.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00183 7th percentileScored 2026-11-07
Fix Fixed pgAdmin 4 (pgadmin.org): 9.19

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
pgadmin.orgpgAdmin 4before 9.199.19Patch availableCNA
  • pgAdmin 4 Vendorpgadmin.org Affected before 9.19 Fixed in 9.19 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:*:*:*——pgadmin.org
  • cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:*:*:* Versions — — ·pgadmin.org

Remediation

Upgrade pgAdmin 4 to version 9.19 or later, which is the fixed version listed for this product.

Written with Claude Haiku 5.5 from the sources below · 2026-11-05

  • Fix · CNA pgAdmin 4 (pgadmin.org) Fixed in 9.19

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    pgadmin.org pgAdmin 4 9.19

    15 records Highest priority Priority MEDIUM 3 MEDIUM, 12 LOW

    Other records, highest priority first

    • TI-2026-83355 Command execution via backslash bypass in pgAdmin 4 query exportPriority MEDIUM 42
    • TI-2026-83352 Failed login limit bypass in pgAdmin 4 allows unlimited password guessingPriority MEDIUM 42
    • TI-2026-83353 pgAdmin 4 LDAP or Kerberos login opens another account by usernamePriority MEDIUM 41

Timeline

  1. 2026-10-30 Threatist record created from CVE-2026-116249
  2. 2026-10-30 Alias added: GHSA-hw9h-5hmm-63g6
  3. 2026-11-01 Priority changed: MEDIUM → LOW
  4. 2026-11-06 CISA SSVC decision points changed

References

  • TI-2024-01901 Unsafe Deserialisation and Remote Code Execution by an Authenticated user in pgAdmin 4 CVSS 3.1CRITICAL 9.9
  • TI-2024-02918 Remote Code Execution Vulnerability through the validate binary path API in pgAdmin 4 CVSS 3.1CRITICAL 9.8
  • TI-2022-03867 Code injection in pgadmin4 CVSS 3.1HIGH 8.8
  • TI-2026-06875 pgAdmin 4: Cross-user data access and shared-server privilege escalation in server mode CVSS 4.0CRITICAL 9.4
  • TI-2025-02572 pgAdmin 4: Remote Code Execution in Query Tool and Cloud Deployment CVSS 3.1CRITICAL 9.9
  • TI-2023-00228 Path traversal in pgadmin CVSS 3.1MEDIUM 6.5
See all 62 →

Sources