PGADMIN4 · CVE-2026-7813 · Package
FIX → 9.15
pgAdmin 4 in server mode fetched user-owned servers, server groups, background processes and debugger arguments without checking the requesting user, so an authenticated user could read other users' objects by guessing IDs. The Shared Servers feature also leaked credentials and let non-owners write a shell command (passexec_cmd) that runs in the owner's connection process.
first public May 11, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Exposed when pgAdmin 4 runs in server mode with more than one user, since the flaw is in per-user access checks. Desktop-mode installs with a single user are not the target. The attacker needs a valid account on the pgAdmin instance; the Shared Servers feature widens the impact to command execution in the owner's connection context.
Not affected if auth-required, desktop-mode, single-user
Who cares pgadmin4, postgresql, python, self-hosted
pip show pgadmin4 and confirm it is at least 9.15.Upgrade to 9.15
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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
9.15GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.