Live › vulnerability › CVE-2026-116250
In server mode, pgAdmin 4 checks a user-supplied file path but then opens it by name, so a swapped-in symbolic or hard link can redirect reads and writes outside the storage directory. An attacker who can plant such links in the storage directory could read, overwrite or load files as the pgAdmin operating-system account.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 20:25 UTC. All times on this page are UTC.
Only pgAdmin 4 instances running in server mode are affected, and only when the storage directory is writable by another operating-system user, such as on a shared or network-mounted volume. Desktop-mode installs and deployments with private, pgAdmin-owned storage are much less exposed. The sources do not say how practical the race is in real deployments.
No product ranges from the sources yet.
pgadmin4 --version or the package manager, and confirm whether it is older than 9.19SERVER_MODE)9.19 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
In server mode pgAdmin 4 validates a path a user gives for a file in their storage directory with check_access_permission() and then opened it by name. Several places opened it with a plain open() or handed the path to a utility that opened it later: the servers.json export and import and the import file listing, and the files given to pg_dump, pg_dumpall, pg_restore and psql by Backup, Restore and Import/Export Data. A symbolic link swapped in at the file or at any parent directory between the check and the open redirected the operation outside the storage directory, so a file could be written, overwritten or read, or loaded into a table, as the operating-system account running pgAdmin. A hard link to an outside file, which O_NOFOLLOW does not detect, and a FIFO, which could hang a request, had the same effect. CVE-2026-86861 fixed this for the File Manager's save_file; these were the remaining paths.
Exploitation requires creating such a link or FIFO inside the user's storage directory. pgAdmin offers no way to do so, and the per-user storage directories belong to the pgAdmin account, so this requires write access to the storage backend as a different operating-system user, for example a shared or network-mounted storage directory, and winning the race.
The fix opens each file by walking down from the storage directory one component at a time with O_NOFOLLOW, accepting only a regular file with one link, and passes the utilities the open descriptor (/dev/fd/N) on Linux. Error messages no longer include the server path.
This issue affects pgAdmin 4: before 9.19.
This page as .md · .json · in your agent: get_signal("CVE-2026-116250")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.