Read the docs

Utility binary path in pgAdmin 4 can point at shared storage

Priority LOW 36CWE-426Published · Updated

Key facts

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

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-426.

Summary

pgAdmin 4 before 9.19 runs pg_dump, pg_restore, pg_dumpall and psql from a binary path that a user sets in preferences. In server mode, the path check covered only the per-user storage directory and not shared storage directories that ordinary users can upload files to, so a user can point the binary path at an uploaded executable. An authenticated user with low privileges can then have pgAdmin run that file as the operating system account running pgAdmin, and the flaw is exploitable where any file with an executable name can run, such as Windows server mode.

Written with Claude Haiku 5.5 from the sources below · 2026-10-31

Description from the CNA

pgAdmin 4 runs pg_dump, pg_restore, pg_dumpall and psql from the binary path a user sets in their preferences. In server mode the binary path was refused only when it lay under the per-user storage directory (STORAGE_DIR), not under a SHARED_STORAGE directory, which ordinary users can upload files to. A user could therefore upload an executable to shared storage, point their binary path at it, and have pgAdmin run it as the operating-system account running pgAdmin. On POSIX, files created through pgAdmin are not executable, so this is exploitable where any file with an executable name can run, such as Windows server mode. The fix checks the binary path against every SHARED_STORAGE directory as well, after expanding $DIR, collapsing ".." and resolving symbolic links, compares directories in a way a different spelling on a case-insensitive filesystem cannot bypass, refuses a path containing a NUL, and enforces the check wherever binary paths are resolved, including for the PSQL tool. This issue affects pgAdmin 4: before 9.19.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00332 26th 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 configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:*:*:*before 9.19Vulnerablepgadmin.org
  • cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:*:*:* Versions before 9.19 Vulnerable ·pgadmin.org

Remediation

Upgrade pgAdmin 4 to version 9.19 or later, which checks binary paths against shared storage directories as well.

Written with Claude Haiku 5.5 from the sources below · 2026-10-31

  • 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-116243
  2. 2026-10-30 Alias added: GHSA-7pw4-4xp2-3398
  3. 2026-11-01 Priority changed: MEDIUM → LOW
  4. 2026-11-04 CVSS score added · NVD
  5. 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 56 →

Sources