CVE-2026-17350— pgAdmin 授权问题漏洞
一分钟漏洞结论
影响对象
pgadmin.org pgAdmin 4
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
pgAdmin是pgAdmin组织开源的一个用于开源数据库 PostgreSQL 的开源管理和开发平台。 pgAdmin 4 9.3至9.17之前版本存在授权问题漏洞，该漏洞源于权限检查不一致，权限装饰器仅应用于单个“前门”路由，其他后端路由和Socket.IO处理程序仅检查身份验证而未检查工具权限，可能导致经过身份验证的用户绕过工具级访问控制策略，访问被管理员拒绝的工具功能。
影响版本矩阵 1
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| pgadmin.org | pgAdmin 4 | 9.3< 9.17 |
affected |
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-17350 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
pgAdmin 4: Tool permission bypass via backend routes and Socket.IO handlers
来源: 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.
来源: 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
来源: CVE Program / CVE List V5
Vulnerability Type
授权机制缺失
来源: CVE Program / CVE List V5
Vulnerability Title
pgAdmin 授权问题漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
pgAdmin是pgAdmin组织开源的一个用于开源数据库 PostgreSQL 的开源管理和开发平台。 pgAdmin 4 9.3至9.17之前版本存在授权问题漏洞，该漏洞源于权限检查不一致，权限装饰器仅应用于单个“前门”路由，其他后端路由和Socket.IO处理程序仅检查身份验证而未检查工具权限，可能导致经过身份验证的用户绕过工具级访问控制策略，访问被管理员拒绝的工具功能。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| pgadmin.org | pgAdmin 4 | 9.3 ~ 9.17 | - |
|
二、漏洞 CVE-2026-17350 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-17350 的情报信息
请登录查看更多情报信息。
CVE-2026-17350 补丁与修复 (4)
CVE-2026-17350 厂商安全公告 (1)
同批安全公告 · pgadmin.org · 2026-07-31 · 共 7 条
| CVE-2026-17566 | 9.9 CRITICAL | pgAdmin 输入验证错误漏洞 |
| CVE-2026-17349 | 9.6 CRITICAL | pgAdmin 信任管理问题漏洞 |
| CVE-2026-17351 | 9.0 CRITICAL | pgAdmin 输入验证错误漏洞 |
| CVE-2026-17346 | 8.8 HIGH | pgAdmin SQL注入漏洞 |
| CVE-2026-17347 | 7.5 HIGH | pgAdmin 命令注入漏洞 |
| CVE-2026-17348 | 6.5 MEDIUM | pgAdmin 授权问题漏洞 |
IV. Related Vulnerabilities
V. Comments for CVE-2026-17350
暂无评论