Is CVE-2026-7813 exploited in the wild?

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

How severe is CVE-2026-7813?

Critical severity, with a CVSS score of 9.9, 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-7813?

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

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

Am I affected by CVE-2026-7813?

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-7813: PostgreSQL pgAdmin 4 authorization bypass and RCE in server mode

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

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

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

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

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-7813 · Severity: critical · CVSS 9.9 · Published 2026-05-11

pgAdmin 4, a popular management tool for PostgreSQL databases, contains a critical authorization flaw when running in server mode. An authenticated user could access or modify other users' private server configurations, background processes, and debugger data by guessing object IDs. This could lead to the theft of database credentials, unauthorized access to sensitive data, or the execution of arbitrary commands on the server.

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

Quick answers

Is CVE-2026-7813 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-7813 being exploited in the wild.
How severe is CVE-2026-7813?: Critical severity, with a CVSS score of 9.9, 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-7813?: 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-7813 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-7813?: 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

pgAdmin 4 prior to version 9.15 fails to properly isolate user-owned objects in server mode. Multiple API endpoints fetched objects (Server Groups, Servers, Shared Servers, Background Processes, and Debugger modules) without verifying that the requesting user owned the object, allowing access via ID guessing. Furthermore, the Shared Servers feature allowed non-owners to write to sensitive fields like 'passexec_cmd', which executes shell commands during connection establishment, leading to arbitrary command execution in the context of the owner's process. Other issues included credential leakage of SSL keys and passwords, and data corruption via SQLAlchemy session mutations. The fix introduces a centralized 'server_access' module and 'UserScopedMixin' to enforce strict ownership checks.

Affected products

PostgreSQL pgAdmin 4 before 9.15

Identifiers

CVE-2026-7813
GHSA-h2x2-q2mc-24gw
PYSEC-2026-452

Timeline

2026-05-11: disclosed
2026-05-11: advisory
2026-04-13: patched: Remediation completed across two pull requests.

References

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