Account-lockout bypass via unchecked default login route
Published May 11, 2026 · Updated May 11, 2026
Improper login-attempt restriction in pgAdmin 4 before 9.15 allows remote attackers to bypass INTERNAL account lockout via /login. The automatically registered Flask-Security route accepts credentials without consulting User.locked because inherited lock checks ignore that field. Only locally passworded INTERNAL accounts are exposed, enabling locked-account access with valid credentials and unbounded online password guessing.
Summary
What happened
Improper login-attempt restriction in pgAdmin 4 before 9.15 allows remote attackers to bypass INTERNAL account lockout via /login. The automatically registered Flask-Security route accepts credentials without consulting User.locked because inherited lock checks ignore that field. Only locally passworded INTERNAL accounts are exposed, enabling locked-account access with valid credentials and unbounded online password guessing.
The record
- CVE
- CVE-2026-7820
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- pgAdmin Development Team
- Product
- pgAdmin 4
- Classifications
- CWE-307, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2026CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <9.15
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo