CVE-2026-7813: Vulnerability in pgadmin.org pgAdmin 4
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.
AI Analysis
Technical Summary
CVE-2026-7813 is an authorization vulnerability in pgAdmin 4 server mode that allows authenticated users to access and manipulate other users' private server-related objects by exploiting missing user identity filtering on multiple endpoints. The Shared Servers feature is particularly affected, with issues including credential leakage (such as shell commands and SSL keys), privilege escalation via writable shell commands executed during connection establishment, and owner data corruption due to improper API permissions. The vulnerability enables arbitrary command execution in the owner's process context and unauthorized edits to owner-only fields. The remediation involved centralizing access control through a new server_access module, applying user scoping to models, returning HTTP 410 on access denial, suppressing owner-only fields in API responses for non-owners, and enforcing strict owner-only write permissions. The vulnerability affects all versions of pgAdmin 4 prior to 9.15.
Potential Impact
An authenticated user can bypass authorization controls to access and manipulate private resources belonging to other users, including servers, server groups, background processes, and debugger data. The vulnerability enables exposure of sensitive credentials and allows privilege escalation through writable shell commands, potentially leading to arbitrary command execution within the owner's process context. Additionally, unauthorized modifications to owner-only data fields can corrupt data integrity. The CVSS score of 9.9 indicates critical impact with high confidentiality, integrity, and availability consequences.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The input data indicates that fixes have been implemented in pgAdmin 4 version 9.15 and later, which centralize access control and enforce strict owner-only permissions. Users should upgrade to version 9.15 or later once available. Until then, restrict access to pgAdmin 4 server mode to trusted users only and monitor for suspicious activity related to server and shared server management. No official vendor advisory or patch link is provided in the input data, so consult pgadmin.org for the latest updates.
CVE-2026-7813: Vulnerability in pgadmin.org pgAdmin 4
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-7813 is an authorization vulnerability in pgAdmin 4 server mode that allows authenticated users to access and manipulate other users' private server-related objects by exploiting missing user identity filtering on multiple endpoints. The Shared Servers feature is particularly affected, with issues including credential leakage (such as shell commands and SSL keys), privilege escalation via writable shell commands executed during connection establishment, and owner data corruption due to improper API permissions. The vulnerability enables arbitrary command execution in the owner's process context and unauthorized edits to owner-only fields. The remediation involved centralizing access control through a new server_access module, applying user scoping to models, returning HTTP 410 on access denial, suppressing owner-only fields in API responses for non-owners, and enforcing strict owner-only write permissions. The vulnerability affects all versions of pgAdmin 4 prior to 9.15.
Potential Impact
An authenticated user can bypass authorization controls to access and manipulate private resources belonging to other users, including servers, server groups, background processes, and debugger data. The vulnerability enables exposure of sensitive credentials and allows privilege escalation through writable shell commands, potentially leading to arbitrary command execution within the owner's process context. Additionally, unauthorized modifications to owner-only data fields can corrupt data integrity. The CVSS score of 9.9 indicates critical impact with high confidentiality, integrity, and availability consequences.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The input data indicates that fixes have been implemented in pgAdmin 4 version 9.15 and later, which centralize access control and enforce strict owner-only permissions. Users should upgrade to version 9.15 or later once available. Until then, restrict access to pgAdmin 4 server mode to trusted users only and monitor for suspicious activity related to server and shared server management. No official vendor advisory or patch link is provided in the input data, so consult pgadmin.org for the latest updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- PostgreSQL
- Date Reserved
- 2026-05-04T21:26:55.716Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a01f792cbff5d86102f20f3
Added to database: 5/11/2026, 3:36:50 PM
Last enriched: 5/11/2026, 3:52:13 PM
Last updated: 5/11/2026, 7:12:57 PM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.