Is CVE-2026-7819 exploited in the wild?

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

How severe is CVE-2026-7819?

High severity, with a CVSS score of 8.1, published 11 May 2026.

Which products and versions are affected?

PostgreSQL pgAdmin 4 < 9.15, before 9.15; pgadmin4 (PyPI) < 9.15, ECOSYSTEM:introduced=0,fixed=9.15.

Is there a fix for CVE-2026-7819?

Yes. pgadmin4 (PyPI): upgrade to 9.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-7819 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-7819?

Check whether you run PostgreSQL pgAdmin 4 or pgadmin4 (PyPI) 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-7819: PostgreSQL pgAdmin 4 symbolic-link path traversal in File Manager

Q: Is there a fix for CVE-2026-7819?

Yes. pgadmin4 (PyPI): upgrade to 9.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-7819 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-7819?

Check whether you run PostgreSQL pgAdmin 4 or pgadmin4 (PyPI) 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-7819 · Severity: high · CVSS 8.1 · Published 2026-05-11

pgAdmin 4 is a popular management tool for PostgreSQL databases. A vulnerability in its File Manager component allows an authenticated user to bypass security restrictions and write files to unauthorized locations on the server. This could lead to data corruption, service disruption, or unauthorized system modifications by overwriting critical configuration files.

Technologies: PostgreSQL pgAdmin 4, pgadmin4 (PyPI). Vendors: PostgreSQL, PyPI.

Quick answers

Is CVE-2026-7819 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-7819 being exploited in the wild.
How severe is CVE-2026-7819?: High severity, with a CVSS score of 8.1, published 11 May 2026.
Which products and versions are affected?: PostgreSQL pgAdmin 4 < 9.15, before 9.15; pgadmin4 (PyPI) < 9.15, ECOSYSTEM:introduced=0,fixed=9.15.
Is there a fix for CVE-2026-7819?: Yes. pgadmin4 (PyPI): upgrade to 9.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-7819 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-7819?: Check whether you run PostgreSQL pgAdmin 4 or pgadmin4 (PyPI) 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

pgadmin4 (PyPI): upgrade to 9.15 or later
```
pip install "pgadmin4>=9.15"
```

Technical details

A symbolic link (symlink) path traversal vulnerability (CWE-61, CWE-22) exists in the pgAdmin 4 File Manager. The 'check_access_permission' function utilized 'os.path.abspath', which resolves parent directory references ('..') but fails to resolve symbolic links. Because subsequent kernel-level write operations follow symlinks, an authenticated attacker can create a symlink within their assigned storage directory that points to a location outside of it. By inducing the application to write to this symlink, the attacker can overwrite any file the pgAdmin process has permissions to access. The fix involves migrating to 'os.path.realpath' for path validation and implementing 'O_NOFOLLOW' during file creation to prevent Time-of-Check to Time-of-Use (TOCTOU) exploits.

Affected products

PostgreSQL pgAdmin 4 < 9.15

Identifiers

CVE-2026-7819
GHSA-hr4r-fwpv-c95j
PYSEC-2026-2868

Timeline

2026-05-01: other: Issue opened on GitHub
2026-05-11: advisory: NVD and GitHub Advisory published
2026-05-11: patched: Fixed in version 9.15

References

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