CVE-2026-116239— pgAdmin 4 LDAP/Kerberos 登录账户混淆漏洞
一分钟漏洞结论
影响对象
pgadmin.org pgAdmin 4
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在服务器模式下，pgAdmin 4 会为每个认证源维护独立的账户记录，因此同一用户名可能同时存在于不同的认证源中（例如，既作为内部账户存在，也作为 LDAP 账户存在）。当用户通过 LDAP 或 Kerberos 完成认证后，pgAdmin 仅凭用户名选择登录账户，或直接沿用 Flask-Security 登录表单查询到的账户，而未验证该账户是否源自实际完成认证的那个认证源。这导致会话被错误地关联到另一个账户，从而继承了该账户的角色、服务器列表以及已保存的数据库密码： 若某 LDAP 或 Kerberos 用户的用
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-116239 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
pgAdmin 4: An LDAP or Kerberos login is logged in to another account with the same username
来源: CVE Program / CVE List V5
Vulnerability Description
In server mode pgAdmin 4 keeps an account per authentication source, so the same username can exist as, for example, an internal account and an LDAP account. After LDAP or Kerberos authenticated a user, pgAdmin chose the account to log in by username alone, or took the account Flask-Security's login form had looked up, without checking that it came from the source that authenticated the user. The session therefore belonged to another account, with its role, its servers and its saved database passwords:
- An LDAP or Kerberos user whose username matched an internal account was logged in as that internal account, including the administrator account created when pgAdmin is first set up.
- With internal authentication listed before LDAP or Kerberos in AUTHENTICATION_SOURCES, the login form's internal validation looks up the account whose email was typed and keeps it even though its password does not match. A Kerberos user could type another Kerberos user's principal and be logged in as that user, and an LDAP user could do the same with an LDAP account whose email is their username.
Exploitation requires valid credentials for an LDAP directory or Kerberos realm that pgAdmin is configured to use.
The fix looks the account up by the authenticated username and the source that authenticated it, and no longer uses the account the login form found for any source but internal authentication. Internal authentication logs in that account only if it is an internal account. Desktop mode is not affected.
This issue affects pgAdmin 4: before 9.19.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
认证机制不恰当
来源: CVE Program / CVE List V5
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| pgadmin.org | pgAdmin 4 | 0 ~ 9.19 | - |
|
二、漏洞 CVE-2026-116239 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-116239 的情报信息
请登录查看更多情报信息。
CVE-2026-116239 其他参考 (3)
-
https://github.com/pgadmin-org/pgadmin4/issues/10675 issue-tracking
同批安全公告 · pgadmin.org · 2026-10-30 · 共 15 条
| CVE-2026-116241 | 9.9 CRITICAL | pgAdmin 4 导入导出数据远程命令执行漏洞 |
| CVE-2026-116249 | 8.4 HIGH | pgAdmin 4 连接文件路径和参数键越界漏洞 |
| CVE-2026-116247 | 8.2 HIGH | pgAdmin 4 身份认证凭证泄露漏洞 |
| CVE-2026-116245 | 8.2 HIGH | pgAdmin 4 服务器模式连接服务未受限漏洞 |
| CVE-2026-116242 | 8.2 HIGH | pgAdmin 4 SSH 隧道使用服务账户身份漏洞 |
| CVE-2026-116244 | 8.2 HIGH | pgAdmin 4 凭据泄露漏洞 |
| CVE-2026-116238 | 8.1 HIGH | pgAdmin 4 认证绕过漏洞 |
| CVE-2026-116243 | 7.5 HIGH | pgAdmin 4 工具二进制路径指向共享存储目录漏洞 |
| CVE-2026-116248 | 6.8 MEDIUM | pgAdmin 4 非管理员共享服务器权限提升漏洞 |
| CVE-2026-116252 | 6.5 MEDIUM | pgAdmin 4 物化视图刷新重定向漏洞 |
| CVE-2026-116250 | 6.5 MEDIUM | pgAdmin 4 存储目录符号链接绕过漏洞 |
| CVE-2026-116246 | 6.5 MEDIUM | pgAdmin 4 服务器密码泄露漏洞 |
| CVE-2026-116240 | 6.5 MEDIUM | pgAdmin 4 文件管理器路径检查绕过漏洞 |
| CVE-2026-116251 | 4.2 MEDIUM | pgAdmin 4 会话未随密码修改失效漏洞 |