CVE-2026-116238— pgAdmin 4 认证绕过漏洞
一分钟漏洞结论
影响对象
pgadmin.org pgAdmin 4
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在服务器模式下，pgAdmin 4 会在连续 MAX_LOGIN_ATTEMPTS 次登录失败（默认为 3 次）后锁定内部账户。然而，该限制可被绕过，导致未认证的攻击者在默认配置下能够对任意内部账户（包括管理员账户）进行无限次密码猜测。具体表现如下： Flask-Security 在 pgAdmin 旁边注册了自有视图。向 Flask-Security 的 视图提交的登录请求，未经 pgAdmin 的失败登录计数或锁定机制检查即被记录并处理；其 视图可无限制地验证已登录用户的密码；其 视图可在未经 pgAdmin
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-116238 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
pgAdmin 4: The failed login limit can be bypassed, and Flask-Security's own views skip pgAdmin's login and password checks
来源: CVE Program / CVE List V5
Vulnerability Description
In server mode pgAdmin 4 locks an internal account after MAX_LOGIN_ATTEMPTS failed logins (3 by default). The limit could be bypassed, giving an unauthenticated attacker an unlimited number of password guesses against any internal account, including the administrator's, in the default configuration:
- Flask-Security registers its own views next to pgAdmin's. A login submitted to its /login view was checked and logged in without pgAdmin's failed login count or lock. Its /verify view checked a signed-in user's password without limit, its /change view changed a password without pgAdmin's change password permission or re-encrypting the user's saved server passwords, and its /reset views sent and applied password resets for accounts that are not internal or are locked.
- The internal account was looked up by its exact username, while the login form matches the email ignoring case, so a login with the username typed in another case was neither counted nor checked for the lock.
- With LDAP or webserver authentication also configured, a wrong internal password was never counted, and with Kerberos or webserver authentication configured a guess could be answered without being counted.
In addition, where accounts from different authentication sources share an email address, a password reset could be sent for, or applied to, an account from another source, and the About box showed the server configuration to a user whose email was that of an administrator's account.
The fix refuses submissions to Flask-Security's own views, counts every failed internal login however the username is typed and whatever other sources are configured, no longer lets a login that posts a password fall back to an authentication source that does not check it, and locks only internal authentication. Password resets and the About box act only on the user's own 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:N/UI:N/S:U/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-116238 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-116238 的情报信息
请登录查看更多情报信息。
CVE-2026-116238 其他参考 (4)
-
https://github.com/pgadmin-org/pgadmin4/issues/10676 issue-tracking
同批安全公告 · pgadmin.org · 2026-10-30 · 共 15 条
| CVE-2026-116241 | 9.9 CRITICAL | pgAdmin 4 导入导出数据远程命令执行漏洞 |
| CVE-2026-116239 | 8.5 HIGH | pgAdmin 4 LDAP/Kerberos 登录账户混淆漏洞 |
| 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-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 会话未随密码修改失效漏洞 |