CVE-2026-7820: pgAdmin 4 Improper Restriction Of Excessive Authentication Vulnerability

MODERATE
Advisory Identifier: GHSA-hv9p-2pqf-r5w3
Share
CVSS 6.5
CWE-307
Published
Advisory Summary

CVE-2026-7820 is a MODERATE (CVSS 6.5) improper restriction of excessive authentication vulnerability (CWE-307: Improper Restriction of Excessive Authentication Attempts) affecting pgAdmin 4 libraries in the PyPI ecosystem. The issue involves improper restriction of excessive authentication attempts. Remediation is available by upgrading affected packages to version 9.15.

CVE-2026-7820 at a Glance

CVE Identifier CVE-2026-7820
GHSA Identifier GHSA-hv9p-2pqf-r5w3
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-307: Improper Restriction of Excessive Authentication Attempts
Affected Product pgAdmin 4
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-7820

To remediate this vulnerability, upgrade all affected pgAdmin 4 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

pgadmin4 fixed: 9.15 
pip install pgadmin4>=9.15
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show pgadmin4

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-7820, inspect your installed packages using pip:

pip show pgadmin4

Analyze the terminal output to locate any version of pgAdmin 4 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.15), your application is affected.

Note: The pip show pgadmin4 command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-307: Improper Restriction of Excessive Authentication Attempts, where the product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame. In pgAdmin 4, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Improper restriction of excessive authentication attempts (CWE-307) in pgAdmin 4. pgAdmin enforces MAX_LOGIN_ATTEMPTS only inside its custom /authenticate/login view. Flask-Security's default /login view, which is registered automatically by security.init_app() and is reachable on every server, never consulted the User.locked field: pgAdmin's User model relied on Flask-Security's UserMixin.is_locked() (which always returns 'not locked') and Flask-Login's is_active (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 MAX_LOGIN_ATTEMPTS. Fix overrides User.is_active and User.is_locked() so the locked column is enforced on every authentication path. LDAP, OAuth2, Kerberos, and Webserver users are not reachable by this bypass because they have no local password and are rejected by Flask-Security's LoginForm.validate before the locked check; the lockout itself is also internal-only (the /authenticate/login view filters by auth_source=INTERNAL). This issue affects pgAdmin 4: before 9.15.

CVE-2026-7820 Affected pgAdmin 4 Versions

1 component(s)
Fixed Versions:
9.15
Product / Package Ecosystem Affected Versions Fixed Version
pgadmin4
pypi/pgadmin4
PyPI
< 9.15
9.15

References

NVD — CVE-2026-7820 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-7820
pgAdmin 4 Source Repository REPOSITORY
https://github.com/pgadmin-org/pgadmin4/issues/9904
Security Fix Commit FIX COMMIT
https://github.com/pgadmin-org/pgadmin4/commit/d336c1e78
pgAdmin 4 Source Repository REPOSITORY
https://github.com/pgadmin-org/pgadmin4

Frequently Asked Questions

What is CVE-2026-7820?
CVE-2026-7820 is a security vulnerability in pgAdmin 4 involving Improper restriction of excessive authentication attempts under CWE-307: Improper Restriction of Excessive Authentication Attempts.
Which pgAdmin 4 versions are affected?
Affected versions include releases prior to 9.15 across affected packages: pgadmin4.
What version fixes CVE-2026-7820?
Upgrading to 9.15 (or the latest patched release for your respective branch) resolves the vulnerability.
Is pgadmin4 affected?
Yes, pgadmin4 is affected in releases prior to 9.15. Upgrade your dependency to 9.15 or later.
What is the CVSS score of CVE-2026-7820?
CVE-2026-7820 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2026-7820?
CVE-2026-7820 is classified under CWE-307: Improper Restriction of Excessive Authentication Attempts (The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.).
How can I check PyPI dependencies for CVE-2026-7820?
Run the dependency tree command: 'pip show pgadmin4'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hv9p-2pqf-r5w3",
  "modified" : "2026-05-18T15:02:31Z",
  "published" : "2026-05-11T18:31:44Z",
  "aliases" : [ "CVE-2026-7820" ],
  "summary" : "pgAdmin 4: Improper restriction of excessive authentication attempts",
  "details" : "Improper restriction of excessive authentication attempts (CWE-307) in pgAdmin 4.\n\npgAdmin enforces MAX_LOGIN_ATTEMPTS only inside its custom /authenticate/login view. Flask-Security's default /login view, which is registered automatically by security.init_app() and is reachable on every server, never consulted the User.locked field: pgAdmin's User model relied on Flask-Security's UserMixin.is_locked() (which always returns 'not locked') and Flask-Login's is_active (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 MAX_LOGIN_ATTEMPTS.\n\nFix overrides User.is_active and User.is_locked() so the locked column is enforced on every authentication path. LDAP, OAuth2, Kerberos, and Webserver users are not reachable by this bypass because they have no local password and are rejected by Flask-Security's LoginForm.validate before the locked check; the lockout itself is also internal-only (the /authenticate/login view filters by auth_source=INTERNAL).\n\nThis issue affects pgAdmin 4: before 9.15.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "pgadmin4"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "9.15"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-7820"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pgadmin-org/pgadmin4/issues/9904"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pgadmin-org/pgadmin4/commit/d336c1e78"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/pgadmin-org/pgadmin4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-307" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-18T15:02:31Z",
    "nvd_published_at" : "2026-05-11T16:17:39Z"
  }
}