# pgAdmin 4: Improper restriction of excessive authentication attempts

Advisory record · `GHSA-hv9p-2pqf-r5w3`

- **Identifiers:** `GHSA-hv9p-2pqf-r5w3` · `CVE-2026-7820` · `PYSEC-2026-2869`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-307](https://cwe.mitre.org/data/definitions/307.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 11 May 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 11 May 2026, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pgadmin4` (PyPI): affected `<9.15`; fixed in `9.15`

## 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.

Written 1 Nov 2026.

## 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

- 6.9 Medium, CVSS 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`, from 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](https://osv.dev/vulnerability/GHSA-hv9p-2pqf-r5w3)

## Sources

- [GitHub Advisory Database: GHSA-hv9p-2pqf-r5w3](https://github.com/advisories/GHSA-hv9p-2pqf-r5w3)
- [OSV: GHSA-hv9p-2pqf-r5w3](https://osv.dev/vulnerability/GHSA-hv9p-2pqf-r5w3)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-7820>
- <https://github.com/pgadmin-org/pgadmin4/issues/9904>
- <https://github.com/pgadmin-org/pgadmin4/commit/d336c1e78>
- <https://github.com/pgadmin-org/pgadmin4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hv9p-2pqf-r5w3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hv9p-2pqf-r5w3/>. Everything for agents: <https://agentprime.io/llms.txt>.
