CVE-2026-116240

pgAdmin 4: File Manager and storage-path tools act on a different path from the one checked

Published Oct 30, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
Description
In server mode pgAdmin 4 validates a path into the user's storage directory with check_access_permission(), which builds the absolute path with get_abs_path(). Several callers then acted on a path they built differently, so the path checked and the path used could name different files:

- Opening a file in the Query Tool, the Google client secret and, on Windows, Import/Export Data, Backup, Restore and saving a file joined the path to the storage directory after stripping leading slashes and backslashes. On POSIX a path checked as a name inside storage could become an absolute path once stripped, so any file the pgAdmin account can read could be opened; on Windows a path naming a drive discarded the storage directory, so these could read, or write, outside it.
- Listing a folder decoded the path a second time after the check, so a folder named like an encoded "..", which a user can create, listed any directory on the host.
- Download, delete, rename and the file-exists check appended the path to the storage directory without a separator, so in a deployment where one user's storage directory name is a prefix of another's, another user's files could be read, deleted or moved; download also checked the path appended to itself.
- Creating a folder could create one in another user's directory.

The fix makes check_access_permission() return the path it checked and every caller act on that path, decodes folder paths once, and opens, deletes and renames files relative to directories opened from the storage directory without following symbolic links. Desktop mode is not affected.

This issue affects pgAdmin 4: before 9.19.

Analysis

AI-generated

Technical impact

The vulnerability arises from a mismatch between the path validated by check_access_permission() and the path used by several file‑manager operations in server mode of pgAdmin 4. Because the validated path is not the same as the one actually acted upon, an attacker can supply a crafted path that resolves to files or directories outside the intended user storage area. The flaw permits reading, writing, deleting, or renaming arbitrary files that the pgAdmin service has permission to access, as well as enumerating arbitrary directories when special encoded paths are used. This leads to confidentiality and integrity violations and could serve as a foothold for further compromise.

Affected Systems

pgAdmin 4 from pgadmin.org, versions prior to 9.19. The bug is fixed in version 9.19 and later. Desktop mode is not affected, and the issue only exists in server mode configurations.

Risk and Exploitability

The CVSS score of 7.1 classifies the risk as high. No EPSS score is available and the vulnerability is not listed in CISA’s KEV catalog. The likely attack vector involves a legitimate authenticated user accessing the web interface of a deployed pgAdmin 4 server and invoking the file‑manager, import/export, backup/restore, or Query Tool functions that rely on the flawed path handling. Successful exploitation would allow the attacker to read or modify sensitive host files, delete or rename other users’ data, or list arbitrary directories, thereby compromising confidentiality, integrity, and availability on the host system.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade pgAdmin 4 to version 9.19 or later, which corrects the path validation and usage mismatch.
  • If an immediate upgrade is infeasible, disable server‑mode features that expose the file manager, import/export, backup/restore, and directory‑listing functionality, limiting user access to only essential operations.
  • Apply strict operating‑system permissions to the pgAdmin data directories and ensure the service runs with the least privilege needed to reduce the impact scope.
  • Monitor server logs for anomalous file‑access attempts and anomalous use of the Query Tool that could indicate exploitation attempts.

Generated by OpenCVE AI on October 30, 2026 at 21:49 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
CPEs cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Pgadmin
Pgadmin pgadmin 4
Vendors & Products Pgadmin
Pgadmin pgadmin 4
Type Values Removed Values Added
Description In server mode pgAdmin 4 validates a path into the user's storage directory with check_access_permission(), which builds the absolute path with get_abs_path(). Several callers then acted on a path they built differently, so the path checked and the path used could name different files: - Opening a file in the Query Tool, the Google client secret and, on Windows, Import/Export Data, Backup, Restore and saving a file joined the path to the storage directory after stripping leading slashes and backslashes. On POSIX a path checked as a name inside storage could become an absolute path once stripped, so any file the pgAdmin account can read could be opened; on Windows a path naming a drive discarded the storage directory, so these could read, or write, outside it. - Listing a folder decoded the path a second time after the check, so a folder named like an encoded "..", which a user can create, listed any directory on the host. - Download, delete, rename and the file-exists check appended the path to the storage directory without a separator, so in a deployment where one user's storage directory name is a prefix of another's, another user's files could be read, deleted or moved; download also checked the path appended to itself. - Creating a folder could create one in another user's directory. The fix makes check_access_permission() return the path it checked and every caller act on that path, decodes folder paths once, and opens, deletes and renames files relative to directories opened from the storage directory without following symbolic links. Desktop mode is not affected. This issue affects pgAdmin 4: before 9.19.
Title pgAdmin 4: File Manager and storage-path tools act on a different path from the one checked
Weaknesses CWE-22
CWE-367
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition

Sources

Status
PUBLISHED
Assigner
PostgreSQL
Published
Updated
Nov 6, 2026, 4:09 PM
Reserved
Oct 25, 2026, 4:26 PM
Status
Analyzed
Published
Oct 30, 2026, 8:17 PM
Modified
Nov 6, 2026, 5:17 PM