Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
pgAdmin 4 before 9.15 is vulnerable: its account lockout after repeated failed logins is only enforced on the custom /authenticate/login path, while the default Flask-Security /login path ignores it. An attacker who can reach the server over the network can obtain a session for an INTERNAL-authenticated account by submitting valid credentials to /login after a lockout, and can also guess passwords there without rate limiting. Upgrade to pgAdmin 4 version 9.15 or later. The source gives no workaround.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.9 | Medium | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N | CNA (PostgreSQL) |
- CISA KEV Not listed.
- EPSS 0.0021, the 11th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:11 UTC First seen by agentprime
- 31 Oct 2026, 14:11 UTC Confirmed by OSV