Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-17350— pgAdmin 4: Tool permission bypass via backend routes and Socket.IO handlers

Quick assessment

Affected
pgadmin.org pgAdmin 4
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

pgAdmin是pgAdmin组织开源的一个用于开源数据库 PostgreSQL 的开源管理和开发平台。 pgAdmin 4 9.3至9.17之前版本存在授权问题漏洞，该漏洞源于权限检查不一致，权限装饰器仅应用于单个“前门”路由，其他后端路由和Socket.IO处理程序仅检查身份验证而未检查工具权限，可能导致经过身份验证的用户绕过工具级访问控制策略，访问被管理员拒绝的工具功能。

CVSS 5.4 · Medium EPSS 0.38% · P29

Affected Version Matrix 1

VendorProduct Version RangeStatus
pgadmin.org pgAdmin 4 9.3< 9.17 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-17350

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
pgAdmin 4: Tool permission bypass via backend routes and Socket.IO handlers
Source: CVE Program / CVE List V5
Vulnerability Description
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 user who had valid pgAdmin login and a stored, working database connection, but had been explicitly denied a specific tool's permission by an administrator, could therefore still drive that tool end-to-end through its other routes and sockets, including obtaining an interactive psql session over the /pty Socket.IO namespace and invoking backup/restore/maintenance/import-export jobs. Because the bypass only restores access to tools operating over the user's own already-authenticated database connection, it does not grant the user any database privilege they did not already hold; it circumvents pgAdmin's own tool-level access-control policy (an organisational segregation-of-duties control, separate from database-level authorization), letting a user reach a pgAdmin feature an administrator intended to withhold from them, using capabilities their existing database role already permits through other means. Socket.IO event handlers had no permission-aware equivalent of permissions_required; only socket_login_required existed, checking authentication but not the tool permission. Fix adds a socket_permissions_required decorator (mirroring permissions_required, honouring the Administrator bypass, reading permissions via has_permission()) and applies it, alongside permissions_required, as the outermost decorator on every backend route and Socket.IO handler for the affected tools. Regression tests assert 403 on every gated route and socket handler for a permission-less user. This issue affects pgAdmin 4 in SERVER mode: from 9.3 before 9.17.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制缺失
Source: CVE Program / CVE List V5
Vulnerability Title
pgAdmin 授权问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
pgAdmin是pgAdmin组织开源的一个用于开源数据库 PostgreSQL 的开源管理和开发平台。 pgAdmin 4 9.3至9.17之前版本存在授权问题漏洞，该漏洞源于权限检查不一致，权限装饰器仅应用于单个“前门”路由，其他后端路由和Socket.IO处理程序仅检查身份验证而未检查工具权限，可能导致经过身份验证的用户绕过工具级访问控制策略，访问被管理员拒绝的工具功能。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
pgadmin.org pgAdmin 4 9.3 ~ 9.17 -

II. Public POCs for CVE-2026-17350

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-17350

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-17350 (4)

Vendor Advisories for CVE-2026-17350 (1)

Same Patch Batch · pgadmin.org · 2026-07-31 · 7 CVEs total

CVE-2026-17566 9.9 CRITICAL pgAdmin 4: RCE via backslash-escape mismatch in Import/Export Data query guard (incomplete
CVE-2026-17349 9.6 CRITICAL pgAdmin 4: Adhoc server clone leaks another user's stored database credentials and ownersh
CVE-2026-17351 9.0 CRITICAL pgAdmin 4: AI Assistant read-only transaction bypass via sqlparse/PostgreSQL lexer disagre
CVE-2026-17346 8.8 HIGH pgAdmin 4: SQL injection via unescaped object names in index Statistics and publication/su
CVE-2026-17347 7.5 HIGH pgAdmin 4: OS command injection in MASTER_PASSWORD_HOOK via untrusted username substitutio
CVE-2026-17348 6.5 MEDIUM pgAdmin 4: Missing authentication decorator on Constraints, preferences, Debugger and Sche

IV. Related Vulnerabilities

Same product: pgAdmin 4
Same vendor: pgadmin.org
Same weakness: CWE-862

V. Comments for CVE-2026-17350

No comments yet

Leave a comment