https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 21:35:40 +0000 https://cve.radiocsirt.org/vuln/cve-2026-7813 <p><strong>Affected:</strong> pgadmin.org pgAdmin 4</p> <p>Authorization vulnerability in pgAdmin 4 server mode affecting Server Groups, Servers, Shared Servers, Background Processes, and Debugger modules.</p> <p>Multiple endpoints fetched user-owned objects without filtering by the requesting user&#39;s identity. An authenticated user could access another user&#39;s private servers, server groups, background processes, and debugger function arguments by guessing object IDs.</p> <p>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&#39;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&#39;s record.</p> <p>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.</p> <p>This issue affects pgAdmin 4: before 9.15.</p> <p><strong>Affected:</strong> pgadmin.org pgAdmin 4</p> <p>Authorization vulnerability in pgAdmin 4 server mode affecting Server Groups, Servers, Shared Servers, Background Processes, and Debugger modules.</p> <p>Multiple endpoints fetched user-owned objects without filtering by the requesting user&#39;s identity. An authenticated user could access another user&#39;s private servers, server groups, background processes, and debugger function arguments by guessing object IDs.</p> <p>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&#39;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&#39;s record.</p> <p>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.</p> <p>This issue affects pgAdmin 4: before 9.15.</p> https://cve.radiocsirt.org/vuln/cve-2026-7813 https://cve.radiocsirt.org/vuln/ghsa-h2x2-q2mc-24gw <p><strong>Affected:</strong> PyPI: pgadmin4</p> <p>Authorization vulnerability in pgAdmin 4 server mode affecting Server Groups, Servers, Shared Servers, Background Processes, and Debugger modules.</p> <p>Multiple endpoints fetched user-owned objects without filtering by the requesting user&#39;s identity. An authenticated user could access another user&#39;s private servers, server groups, background processes, and debugger function arguments by guessing object IDs.</p> <p>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&#39;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&#39;s record.</p> <p>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.</p> <p>This issue affects pgAdmin 4: before 9.15.</p> <p><strong>Affected:</strong> PyPI: pgadmin4</p> <p>Authorization vulnerability in pgAdmin 4 server mode affecting Server Groups, Servers, Shared Servers, Background Processes, and Debugger modules.</p> <p>Multiple endpoints fetched user-owned objects without filtering by the requesting user&#39;s identity. An authenticated user could access another user&#39;s private servers, server groups, background processes, and debugger function arguments by guessing object IDs.</p> <p>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&#39;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&#39;s record.</p> <p>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.</p> <p>This issue affects pgAdmin 4: before 9.15.</p> https://cve.radiocsirt.org/vuln/ghsa-h2x2-q2mc-24gw