pgAdmin 4: The failed login limit can be bypassed, and Flask-Security's own views skip pgAdmin's login and password checks

Özet

Türkçe özeti henüz hazır değil; şimdilik kaynağın kendi açıklamasını gösteriyoruz.

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.

Etkilenen sürümler1 yazılım

Kaynaklar6 kaynak

• CVE.org kaydı
• NVD kaydı
• github.com/…ommit/58c531d831179dc9b0a5bf873ccb80c71c8d387a Yama
• github.com/…ommit/35c9235d17a7d5a99778f01b2f1b9e5e3a3b7fde Yama
• github.com/…ommit/c6ef41a951012cd877a1992b5dac681eec36e48d Yama
• github.com/pgadmin-org/pgadmin4/issues/10676 Üçüncü taraf

Kayıt geçmişi

1. 30 Eki 2026 22:55Yayımlandı

İlgili açıklar

• 6,5 CVE-2026-116252pgAdmin 4: Materialized view refresh redirects its connection through a crafted database name
• 4,2 CVE-2026-116251pgAdmin 4: A user's other sessions survive a change of their password
• 8,4 CVE-2026-116249pgAdmin 4: Connection file paths and parameter keys escape the user's storage directory
• 6,5 CVE-2026-116250pgAdmin 4: Files opened in a storage directory follow a symbolic link, hard link or FIFO planted after the containment check
• 6,8 CVE-2026-116248pgAdmin 4: Non-administrators can share a server with every user
• 6,5 CVE-2026-116246pgAdmin 4: Server passwords are left in pgAdmin's process environment