pgAdmin 4 CVE-2026-7813: Brief Summary of a Critical Multi Tenant Authorization Bypass in Server Mode

Introduction

A systemic authorization failure in pgAdmin 4's server mode let any authenticated user reach across tenant boundaries and access other users' private database servers, credentials, and background processes by guessing numeric object IDs. Worse, the Shared Servers feature opened a path to arbitrary command execution. An attacker could write a malicious shell command into another user's connection configuration, and pgAdmin would execute it the next time that user connected to their database.

pgAdmin 4 is the most popular and feature-rich open source administration and development platform for PostgreSQL. PostgreSQL is widely adopted across industries, and pgAdmin 4 deployments in server (multi-tenant) mode are common in enterprise environments. This vulnerability is particularly relevant to database administrators and security teams that manage shared infrastructure.

Technical information

Cross-user data access via object ID guessing

The root cause of CVE-2026-7813 is that multiple API endpoints in pgAdmin 4 server mode fetched user-owned objects without filtering by the requesting user's identity. The affected modules include Server Groups, Servers, Shared Servers, Background Processes, and the Debugger. Because object IDs are sequential integers, an authenticated user could trivially enumerate and retrieve private assets belonging to other users.

The development team identified and replaced approximately 20 scattered unfiltered queries and fixed over 155 unguarded callers at the connection manager chokepoint. Those numbers describe a systemic absence of tenant scoping across the application's data access layer, rather than a single missed authorization check.

Shared server privilege escalation

The Shared Servers feature added several more attack vectors on top of the authorization failure.

Arbitrary command execution via passexec_cmd: The passexec_cmd field stores a shell command that pgAdmin executes when it establishes a database connection (it is used to retrieve passwords dynamically). Non-owners could write to this field through the API. An attacker could set passexec_cmd to a malicious command on a Shared Server, and when the legitimate owner next connected to that server, the attacker's command would execute in the owner's process context.

Credential leakage: Owner SSL file paths, passfile data, and passexec_cmd values were exposed in connection parameters during Shared Server creation and property merges. Any user with access to the shared server record could see these database authentication secrets.

Owner data corruption via SQLAlchemy session mutations: Several fields had no per-user persistence at all. When a non-owner edited fields such as kerberos_conn, tags, or post_connection_sql, the changes mutated the owner's record directly through SQLAlchemy session side effects. Other owner-only fields (passexec_cmd, passexec_expiration, db_res, db_res_type) were also writable by non-owners through the API, with no write guards.

Attack flow

An attacker exploiting this vulnerability would proceed as follows:

Authenticate to the pgAdmin 4 server mode instance with any valid user account.
Enumerate object IDs across the affected endpoints (Server Groups, Servers, Shared Servers, Background Processes, Debugger) by iterating sequential integer IDs.
Retrieve private server configurations and credentials belonging to other users from the unfiltered API responses.
Optionally, escalate privileges by writing a malicious shell command to the passexec_cmd field of a Shared Server owned by another user.
Wait for the legitimate owner to connect to that server. pgAdmin executes the passexec_cmd value as a shell command, running the attacker's payload in the owner's process context.

The attack requires only a valid authenticated session and the ability to make standard API requests. It needs no special privileges or complex exploitation techniques.

Remediation architecture

The fix, delivered across two pull requests (PR #9830 and PR #9835), made these structural changes to the authorization model:

A new server_access.py module centralizes access control. It replaces the scattered unfiltered queries with guarded functions that enforce strict ownership validation.
A UserScopedMixin.for_user() method was applied across 10 user-owned models, so database queries filter by the current user's ID automatically.
The connection_manager() now raises an ObjectGone exception and returns HTTP 410 when access is denied in server mode, which gives a clear audit signal.
Five new columns were added to the SharedServer model for per-user feature parity, and explicit write guards block non-owners from setting owner-only fields.

Affected systems and versions

This vulnerability affects pgAdmin 4 versions before 9.15 running in server mode (the multi-tenant deployment model). Desktop mode deployments serve a single user by nature and are not affected by the cross-user data access aspects of this vulnerability.

The fix is included in pgAdmin 4 version 9.15, released on May 11, 2026.

Vendor security history

The pgAdmin 4 v9.15 release addressed eight distinct security vulnerabilities (CVE-2026-7813 through CVE-2026-7820) alongside 19 total bug fixes. The security issues spanned several categories, including cross-site scripting, SQL injection, and unsafe deserialization, which indicates a broad security audit was conducted.

This is not the first server mode authorization issue in pgAdmin 4. Earlier in 2026, CVE-2026-1707 disclosed a restore restriction bypass via key disclosure affecting versions up to 9.11. The recurrence of authorization issues in the server mode architecture suggests that organizations deploying pgAdmin 4 in multi-tenant configurations should treat each release as a priority update and consider additional network-level access controls around the pgAdmin instance.

CVE Analysis

Experimental AI-Generated Content

Introduction

Technical information