Is CVE-2026-7818 exploited in the wild?

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

How severe is CVE-2026-7818?

High severity, with a CVSS score of 7, 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-7818?

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-7818 attacked?

It is attacked with local access, in a network appliance.

Am I affected by CVE-2026-7818?

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-7818: PostgreSQL pgAdmin 4 insecure deserialization in FileBackedSessionManager

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

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-7818 attacked?

It is attacked with local access, in a network appliance.

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

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-7818 · Severity: high · CVSS 7 · Published 2026-05-11

pgAdmin 4, a popular management tool for PostgreSQL databases, contains a security flaw in how it handles user session files. An attacker with local access to the system could place a malicious file in the session directory to take full control of the application. This could allow them to execute unauthorized commands on the underlying server with the same permissions as the pgAdmin service.

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

Quick answers

Is CVE-2026-7818 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-7818 being exploited in the wild.
How severe is CVE-2026-7818?: High severity, with a CVSS score of 7, 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-7818?: 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-7818 attacked?: It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-7818?: 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 deserialization of untrusted data vulnerability (CWE-502) exists in the pgAdmin 4 FileBackedSessionManager. The component used Python's standard object-serialization module (pickle) to process session-file contents without first verifying their integrity via HMAC. An authenticated local attacker with write access to the sessions directory—potentially gained through misconfiguration or a separate path-traversal vulnerability—can plant a crafted serialized payload. Upon processing the file, the application executes the payload, leading to remote code execution (RCE) under the pgAdmin process identity. The issue is resolved in version 9.15 by implementing a SHA-256 HMAC check before deserialization and hardening file permissions.

Affected products

PostgreSQL pgAdmin 4 before 9.15

Identifiers

CVE-2026-7818
GHSA-4rhg-h8f2-v4jm
PYSEC-2026-2865

Timeline

2026-05-01: disclosed: Issue reported on GitHub
2026-05-11: advisory: CVE published
2026-05-11: patched: Fixed in version 9.15

References

https://github.com/pgadmin-org/pgadmin4/issues/9901

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