Is CVE-2026-116250 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-116250 being exploited in the wild.

How severe is CVE-2026-116250?

Medium severity, with a CVSS score of 6.5, published 30 October 2026.

Which products and versions are affected?

pgAdmin Project pgAdmin 4 before 9.19.

How is CVE-2026-116250 attacked?

It is attacked with local access, in a web application.

Am I affected by CVE-2026-116250?

Check whether you run pgAdmin Project pgAdmin 4 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-116250: pgAdmin 4 path traversal via symlink in file operations

CVE-2026-116250 · Severity: medium · CVSS 6.5 · Published 2026-10-30

pgAdmin is a web-based administration tool for PostgreSQL databases. In server mode, it performs a security check before opening user-supplied file paths, but fails to prevent symbolic links, hard links, or FIFOs from redirecting operations outside the intended storage directory. An attacker with write access to the storage backend could read, write, or overwrite arbitrary files as the pgAdmin process user, or load data into tables from unintended sources.

Technologies: pgAdmin Project pgAdmin 4. Vendors: pgAdmin Project.

Quick answers

Is CVE-2026-116250 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-116250 being exploited in the wild.
How severe is CVE-2026-116250?: Medium severity, with a CVSS score of 6.5, published 30 October 2026.
Which products and versions are affected?: pgAdmin Project pgAdmin 4 before 9.19.
Is there a fix for CVE-2026-116250?: Yes: fixed in pgAdmin 4 9.19. Until then: Restrict write access to the per-user storage directories to only the pgAdmin process user; avoid use of shared or network-mounted storage for pgAdmin user directories where other OS users may have write access. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-116250 attacked?: It is attacked with local access, in a web application.
Am I affected by CVE-2026-116250?: Check whether you run pgAdmin Project pgAdmin 4 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: pgAdmin 4 9.19

Restrict write access to the per-user storage directories to only the pgAdmin process user; avoid use of shared or network-mounted storage for pgAdmin user directories where other OS users may have write access.

Technical details

The vulnerability exists in multiple code paths that handle file operations: servers.json export/import, import file listing, and file passing to pg_dump, pg_dumpall, pg_restore, and psql. The check_access_permission() function validates the path, but a time-of-check-time-of-use (TOCTOU) race allows an attacker to swap in a symbolic link, hard link, or FIFO between validation and file open, redirecting the operation. Exploitation requires write access to the user's storage directory as a different OS user (e.g., on shared/network storage) and winning a race condition. The fix uses O_NOFOLLOW with component-by-component directory traversal from the storage root and validates that only regular files with a single link are opened.

Affected products

pgAdmin Project pgAdmin 4 before 9.19

Timeline

2026-10-30: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.