CVE-2026-7818: Pgadmin4 PgAdmin 4 Has Deserialization Of Vulnerability

HIGH
Advisory Identifier: GHSA-4rhg-h8f2-v4jm
CVSS 7.0
CWE-502
Published
Advisory Summary

CVE-2026-7818 is a HIGH (CVSS 7.0) pgadmin 4 has deserialization of vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Pgadmin4 libraries in the PyPI ecosystem. The issue involves pgadmin 4 has deserialization of untrusted data in its filebackedsessionmanager. Remediation is available by upgrading affected packages to version 9.15.

CVE-2026-7818 at a Glance

CVE Identifier CVE-2026-7818
GHSA Identifier GHSA-4rhg-h8f2-v4jm
Severity HIGH
CVSS v3.1 Base Score 7.0
CWE Classification CWE-502: Deserialization of Untrusted Data
Affected Product Pgadmin4
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.0

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

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

How to Fix CVE-2026-7818

To remediate this vulnerability, upgrade all affected Pgadmin4 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-7818, inspect your installed packages using pip:

pip show pgadmin4

Analyze the terminal output to locate any version of Pgadmin4 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-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Pgadmin4, 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

Deserialization of untrusted data (CWE-502) in pgAdmin 4 FileBackedSessionManager. The session manager performed unsafe deserialization of session-file contents (using Python's standard object-serialization module) before performing any HMAC integrity check. Any file dropped into the sessions directory was deserialized unconditionally. An authenticated user with write access to the sessions directory (whether by misconfiguration or in combination with another path-traversal flaw) could plant a crafted serialized payload to achieve operating-system level remote code execution under the pgAdmin process identity. Fix prepends a 64-byte hex SHA-256 HMAC over the session body, computed with SECRET_KEY, and verifies it via hmac.compare_digest before any deserialization. The check is raised (rather than asserted) on empty SECRET_KEY so it is not stripped under -O. This issue affects pgAdmin 4: before 9.15.

CVE-2026-7818 Affected Pgadmin4 Versions

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

References

Frequently Asked Questions

What is CVE-2026-7818?
CVE-2026-7818 is a security vulnerability in Pgadmin4 involving pgAdmin 4 has deserialization of untrusted data in its FileBackedSessionManager under CWE-502: Deserialization of Untrusted Data.
Which Pgadmin4 versions are affected?
Affected versions include releases prior to 9.15 across affected packages: pgadmin4.
What version fixes CVE-2026-7818?
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-7818?
CVE-2026-7818 has a CVSS v3.1 base score of 7.0 (HIGH) with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-7818?
CVE-2026-7818 is classified under CWE-502: Deserialization of Untrusted Data (The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.).
How can I check PyPI dependencies for CVE-2026-7818?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4rhg-h8f2-v4jm",
  "modified" : "2026-05-18T15:12:48Z",
  "published" : "2026-05-11T18:31:44Z",
  "aliases" : [ "CVE-2026-7818" ],
  "summary" : "pgAdmin 4 has deserialization of untrusted data in its FileBackedSessionManager",
  "details" : "Deserialization of untrusted data (CWE-502) in pgAdmin 4 FileBackedSessionManager.\n\nThe session manager performed unsafe deserialization of session-file contents (using Python's standard object-serialization module) before performing any HMAC integrity check. Any file dropped into the sessions directory was deserialized unconditionally. An authenticated user with write access to the sessions directory (whether by misconfiguration or in combination with another path-traversal flaw) could plant a crafted serialized payload to achieve operating-system level remote code execution under the pgAdmin process identity.\n\nFix prepends a 64-byte hex SHA-256 HMAC over the session body, computed with SECRET_KEY, and verifies it via hmac.compare_digest before any deserialization. The check is raised (rather than asserted) on empty SECRET_KEY so it is not stripped under -O.\n\nThis issue affects pgAdmin 4: before 9.15.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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-7818"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pgadmin-org/pgadmin4/issues/9901"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pgadmin-org/pgadmin4/commit/30a890337"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/pgadmin-org/pgadmin4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-502" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-18T15:12:48Z",
    "nvd_published_at" : "2026-05-11T16:17:38Z"
  }
}