Loading vulnerability…
CVE-2026-7820 is an improper restriction of excessive authentication attempts vulnerability in pgAdmin 4 affecting versions before 9.15. pgAdmin implemented account lockout enforcement in its custom /authenticate/login handler, but Flask-Security's default /login route remained automatically exposed and did not honor the application's locked-account state. The issue stemmed from the pgAdmin User model relying on Flask-Security's UserMixin.is_locked(), which effectively returned the account as not locked, and Flask-Login's is_active behavior, which checked only whether the account was active and not whether it was locked. As a result, after an INTERNAL account was locked through repeated failures on /authenticate/login, an attacker could still authenticate successfully by submitting valid credentials to /login. The same alternate authentication path also bypassed the intended login-attempt throttling, allowing unrestricted online password guessing against INTERNAL accounts.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.