CVE-2026-17350
published 2026-07-31CVE-2026-17350: The per-tool permission system (custom roles / role-based tool permissions, introduced in pgAdmin 4 9.3) did not enforce its permission check consistently. In…
PriorityP434medium5.4CVSS 3.1
AVNACLPRLUINSUCLILAN
EPSS
0.38%
29.2th percentile
The per-tool permission system (custom roles / role-based tool permissions, introduced in pgAdmin 4 9.3) did not enforce its permission check consistently. In SERVER mode, pgAdmin 4 gates each tool behind a per-tool Flask-Security permission, but the permission decorator (permissions_required) was applied only to a single "front door" route per tool. Every other backend route and Socket.IO handler in that tool's workflow relied solely on pga_login_required/socket_login_required, which check authentication but not the tool permission.
The reporter verified three cases against a test build: (1) a user without tools_query_tool permission received 403 on the protected sqleditor initialization route, but the same session went on to connect the server, initialize the viewdata backend chain, and retrieve real table row content; (2) a user without tools_grant_wizard received 403 on the protected acl route, but the same session still enumerated grantable objects, generated GRANT SQL, and successfully applied it -- confirmed database-side via has_table_privilege(); (3) a user without tools_schema_diff received 403 on the protected panel route, but the same session initialized schema diff, enumerated and connected databases, and obtained real DDL differences via the compare_database Socket.IO handler. The reporter also confirmed a related but distinct issue: a non-owner triggering /misc/workspace/adhoc_connect_server against an administrator-owned shared server caused pgAdmin to persist a new server row still owned by the administrator (user_id/shared unchanged from the source), even though the connection attempt itself reported failure.
During remediation, the same front-door-only permission gap was found to also affect the ERD, PSQL, and Debugger tools, and the Backup, Restore, Maintenance, and Import/Export blueprints, none of which were part of the original report; these were fixed using the same pattern as an extension of the reported defect class.
An authenticated use
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| pgadmin.org | pgadmin_4 | >= 9.3 < 9.17 | 9.17 |
| pgadmin | pgadmin_4 | >= 9.3 < 9.17 | 9.17 |
CVSS provenance
nvdv3.15.4MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
nvdv4.05.3MEDIUMCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vendor_redhat5.4MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
The per-tool permission system (custom roles / role-based tool permissions, introduced in pgAdmin 4 9.3) did not enforce its permission check consistently.
ghsa_unreviewed·2026-07-31
CVE-2026-17350 [MEDIUM] CWE-862 The per-tool permission system (custom roles / role-based tool permissions, introduced in pgAdmin 4 9.3) did not enforce its permission check consistently.
The per-tool permission system (custom roles / role-based tool permissions, introduced in pgAdmin 4 9.3) did not enforce its permission check consistently. In SERVER mode, pgAdmin 4 gates each tool behind a per-tool Flask-Security permission, but the permission decorator (permissions_required) was applied only to a single "front door" route per tool. Every other backend route and Socket.IO handler in that tool's workflow relied solely on pga_login_required/socket_login_required, which check authentication but not the tool permission.
The reporter verified three cases against a test build: (1) a user without tools_query_tool permission received 403 on the protected sqleditor initialization route, but the same session went on to connect the server, initialize the viewdata backend chain, and
VulDB
pgadmin-org pgAdmin up to 9.16 Socket IO adhoc_connect_server has_permission user_id/shared privileges management
vuldb·2026-07-31·CVSS 5.4
CVE-2026-17350 [MEDIUM] pgadmin-org pgAdmin up to 9.16 Socket IO adhoc_connect_server has_permission user_id/shared privileges management
A vulnerability categorized as critical has been discovered in pgadmin-org pgAdmin up to 9.16. This issue affects the function has_permission of the file /misc/workspace/adhoc_connect_server of the component Socket IO Handler. The manipulation of the argument user_id/shared results in improper privilege management.
This vulnerability is reported as CVE-2026-17350. The attack can be launched remotely. No exploit exists.
It is advisable to upgrade the affected component.
Red Hat
pgadmin4: pgAdmin 4: Permission bypass allows authenticated users to access restricted tools
vendor_redhat·2026-07-31·CVSS 5.4
CVE-2026-17350 [MEDIUM] CWE-425 pgadmin4: pgAdmin 4: Permission bypass allows authenticated users to access restricted tools
pgadmin4: pgAdmin 4: Permission bypass allows authenticated users to access restricted tools
The per-tool permission system (custom roles / role-based tool permissions, introduced in pgAdmin 4 9.3) did not enforce its permission check consistently. In SERVER mode, pgAdmin 4 gates each tool behind a per-tool Flask-Security permission, but the permission decorator (permissions_required) was applied only to a single "front door" route per tool. Every other backend route and Socket.IO handler in that tool's workflow relied solely on pga_login_required/socket_login_required, which check authentication but not the tool permission.
The reporter verified three cases against a test build: (1) a user without tools_query_tool permission received 403 on the protected sqleditor initialization route, b
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-17350 pgadmin4: pgAdmin 4: Permission bypass allows authenticated users to access restricted tools [fedora-all]
bugzilla·2026-08-15·CVSS 5.4
CVE-2026-17350 [MEDIUM] CVE-2026-17350 pgadmin4: pgAdmin 4: Permission bypass allows authenticated users to access restricted tools [fedora-all]
CVE-2026-17350 pgadmin4: pgAdmin 4: Permission bypass allows authenticated users to access restricted tools [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
The per-tool permission system (custom roles / role-based tool permissions, introduced in pgAdmin 4 9.3) did not enforce its permission check consistently. In SERVER mode, pgAdmin 4 gates each tool behind a per-tool Flask-Security permission, but the permission decorator (permissions_required) was applied only to a single "front door" route per tool. Every other backend route and Socket.IO handler in that tool's workflow relied solely on pga_login_r
Bugzilla
CVE-2026-17350 pgadmin4: pgAdmin 4: Permission bypass allows authenticated users to access restricted tools
bugzilla·2026-07-31·CVSS 5.4
CVE-2026-17350 [MEDIUM] CVE-2026-17350 pgadmin4: pgAdmin 4: Permission bypass allows authenticated users to access restricted tools
CVE-2026-17350 pgadmin4: pgAdmin 4: Permission bypass allows authenticated users to access restricted tools
The per-tool permission system (custom roles / role-based tool permissions, introduced in pgAdmin 4 9.3) did not enforce its permission check consistently. In SERVER mode, pgAdmin 4 gates each tool behind a per-tool Flask-Security permission, but the permission decorator (permissions_required) was applied only to a single "front door" route per tool. Every other backend route and Socket.IO handler in that tool's workflow relied solely on pga_login_required/socket_login_required, which check authentication but not the tool permission.
The reporter verified three cases against a test build: (1) a user without tools_query_tool permission received 403 on the protected sqleditor initial
https://github.com/pgadmin-org/pgadmin4/commit/461c3afba92baad37c70a6fbd52d205d13a9de53https://github.com/pgadmin-org/pgadmin4/commit/64a9cdbd6a240a962144f84418beaf9e66419779https://github.com/pgadmin-org/pgadmin4/commit/ba1984718ad703011740ad48cb9b82402b89cc2chttps://github.com/pgadmin-org/pgadmin4/commit/d36bd8dc96812c716664feac533d240544e70adchttps://github.com/pgadmin-org/pgadmin4/issues/10190
2026-07-31
Published