dbcve.org
Pgadmin 4Application · Pgadmin

CVE-2026-7813

CRITICAL · 9.9 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 9.15 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authorization vulnerability in pgAdmin 4 server mode affecting Server Groups, Servers, Shared Servers, Background Processes, and Debugger modules. Multiple endpoints fetched user-owned objects without filtering by the requesting user's identity. An authenticated user could access another user's private servers, server groups, background processes, and debugger function arguments by guessing object IDs. Additionally, the Shared Servers feature contained multiple issues including credential leakage (passexec_cmd, passfile, SSL keys), privilege escalation via writable passexec_cmd (a shell command executed when establishing the connection) allowing arbitrary command execution in the owner's process context, and owner-data corruption via SQLAlchemy session mutations. Several owner-only fields (passexec_cmd, passexec_expiration, db_res, db_res_type) were writable by non-owners through the API, and additional fields (kerberos_conn, tags, post_connection_sql) lacked per-user persistence so non-owner edits mutated the owner's record. Fix centralises access control via a new server_access module, scopes all user-owned models with a UserScopedMixin, returns HTTP 410 from connection_manager when access is denied in server mode, suppresses owner-only fields for non-owners across the merge / API response / ServerManager paths, and adds an explicit owner-only write guard. The remediation landed in two pull requests; both are referenced. This issue affects pgAdmin 4: before 9.15.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Critical authorization bypass in pgAdmin 4 server mode where authenticated users could access/modify other users' private objects (servers, server groups, background processes, debugger data) by guessing object IDs. The Shared Servers feature also leaks credentials, allows privilege escalation via writable shell commands (passexec_cmd), and permits non-owners to corrupt owner data through SQLAlchemy session mutations.

MitigationUpgrade pgAdmin 4 to version 9.15 or later to receive the centralized access control fixes, UserScopedMixin implementation, and owner-only field protections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pgadmin 4Application
Affected:< 9.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine if pgAdmin 4 is installed
    Check for pgAdmin 4 installation by looking for the application, Python package, or container. Common methods: check for /usr/lib/pgadmin4 or similar directories, look for pgadmin4 Python package via 'pip list', or check running containers.
    Affected if pgAdmin 4 is installed and running
  2. Identify the installed pgAdmin 4 version
    Retrieve the version number using the appropriate method for your installation: run 'pgAdmin4 --version' or 'pgadmin4 --version' from command line, check the About dialog in the desktop application, or query the Python package with 'pip show pgadmin4' or 'pip list | grep pgadmin'. In server mode, the version may be visible in the web interface footer or via API endpoint.
    Affected if The version is lower than 9.15
  3. Confirm pgAdmin 4 is running in server mode
    Server mode is typically enabled when pgAdmin 4 is accessed via a web browser rather than as a desktop application. Check if the application is serving HTTP/HTTPS requests, typically on port 80/443 or port 5050 (default pgAdmin server port). Verify through process inspection: look for processes like 'pgAdmin4.py' or 'gunicorn' running with server configurations.
    Affected if pgAdmin 4 is running as a web server and the version is below 9.15
  4. Check for Shared Servers configuration
    In pgAdmin 4 server mode, examine if the Shared Servers feature is enabled or in use. This feature allows server objects to be shared between users. Check configuration files (config_local.py or config.py) for SHARED_SERVERS setting, or inspect the web interface under Server menu for shared server groups.
    Affected if Shared Servers feature is enabled and the version is below 9.15

A user is affected if pgAdmin 4 version is below 9.15 AND the application is running in server mode, allowing authenticated users to potentially access other users private objects through object ID guessing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.15 or later
Fixed in 9.15
Vendor patch github.com →
Interim mitigation

Upgrade pgAdmin 4 to version 9.15 or later to receive the centralized access control fixes, UserScopedMixin implementation, and owner-only field protections.

Recommended fix High confidence

pgAdmin 4 version 9.15 or later

  1. 1. Identify the current pgAdmin 4 installation method (pip, container, or system package)
  2. 2. Back up the pgAdmin 4 configuration directory (typically ~/.pgadmin or the configured storage path)
  3. 3. If installed via pip: Run 'pip install --upgrade pgadmin4==9.15' or 'pip install pgadmin4>=9.15'
  4. 4. If using Docker: Pull and redeploy the official pgadmin4 container at version 9.15 or later (e.g., 'docker pull dpage/pgadmin4:9.15')
  5. 5. If using a system package manager (apt, yum): Update the package repository and install the pgAdmin4 version 9.15 package
  6. 6. Verify the upgrade by checking the pgAdmin 4 version in the UI (Help > About pgAdmin 4) or via API
  7. 7. After upgrade, test that users can only access their own objects (server groups, servers, background processes) to confirm the access control fix is working
Caveat Minor: HTTP 410 responses are now returned when users attempt to access connection_manager resources they do not own (previously returned different errors); this is a security behavior change

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pgadmin 4 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7813 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data