pgAdmin 4: Improper restriction of excessive authentication attempts
CVE-2026-7820GHSA-hv9p-2pqf-r5w3
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (pgadmin4 9.15), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI pgadmin4
- Affected
- < 9.15
- Fixed in
- 9.15
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-hv9p-2pqf-r5w3 lists affected ranges: PyPI pgadmin4 >=0 <9.15 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-hv9p-2pqf-r5w3 lists affected ranges: PyPI pgadmin4 >=0 <9.15
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 6.9 · 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 · score source
- EPSS
- CVE-2026-7820: 0.21% estimated exploitation activity in the next 30 days; percentile 11.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Improper restriction of excessive authentication attempts (CWE-307) in pgAdmin 4. pgAdmin enforces MAXLOGINATTEMPTS only inside its custom /authenticate/login view. Flask-Security's default /login view, which is registered automatically by security.initapp() and is reachable on every server, never consulted the User.locked field: pgAdmin's User model relied on Flask-Security's UserMixin.islocked() (which always returns 'not locked') and Flask-Login's isactive (which only checks the active column, not locked). An attacker who triggered an account lockout via /authenticate/login could therefore obtain a session by re-submitting valid credentials directly to /login, defeating the brute-force-protection control for accounts using the INTERNAL authentication source. The same bypass also means that login attempts via /login are never rate-limited, so an attacker can perform an unbounded online password-guessing attack against INTERNAL accounts regardless of MAXLOGINATTEMPTS. Fix overrides…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-hv9p-2pqf-r5w3
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-hv9p-2pqf-r5w3
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-7820 Advisory: pgAdmin 4: Improper restriction of excessive authentication attempts IDs: CVE-2026-7820, GHSA-hv9p-2pqf-r5w3 Record: https://patchnext.com/advisories/cve-2026-7820 (revision 3, source checked 26 Oct 2026, 13:41 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: pgadmin4 9.15. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI pgadmin4: affected < 9.15; fixed in 9.15 ## Suggested inspection (read-only) - `python -m pip show pgadmin4`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on pgadmin4. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-hv9p-2pqf-r5w3 (OSV record GHSA-hv9p-2pqf-r5w3 lists affected ranges: PyPI pgadmin4 >=0 <9.15 (fixed)) - Verified: https://github.com/advisories/GHSA-hv9p-2pqf-r5w3 (GitHub-reviewed advisory GHSA-hv9p-2pqf-r5w3 lists affected ranges: PyPI pgadmin4 >=0 <9.15) Commands are suggestions: review each one before running it.
Loading voting…