CVE-2026-7818: pgAdmin 4: Unsafe deserialization (CWE-502) in file-backed session manager leads to remote code execution

Published May 11, 2026
·
Updated

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 SECRETKEY, and verifies it via hmac.comparedigest before any deserialization. The check is raised (rather than asserted) on empty SECRETKEY so it is not stripped under -O.

This issue affects pgAdmin 4: before 9.15.

Affected Software

2 affected components
pgAdmin pgAdmin 4<9.15
pgAdmin Pgadmin 4 Postgresql<9.15

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pgAdmin 4 FileBackedSessionManager to a version that resolves this vulnerability.

    Fixed in 9.15
  2. Configuration

    Configure pgAdmin so SECRET_KEY is not empty; this preserves the raised check that prevents unsafe deserialization from running when SECRET_KEY is invalid.

    pgAdmin 4 FileBackedSessionManager SECRET_KEY integrity check behavior = Set SECRET_KEY to a non-empty value so the raised (not asserted) HMAC verification is enforced before any deserialization
  3. Compensating control

    Ensure an authenticated user cannot write to the pgAdmin sessions directory (e.g., correct permissions so only the pgAdmin process can write there).

Event History

May 11, 2026
CVE Published
via MITRE·02:35 PM
Data Sourced
via MITRE·02:35 PM
DescriptionSeverity
Data Sourced
via NVD·04:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 23, 58372
Event
via FIRST·11:43 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-7818?

The severity of CVE-2026-7818 is classified as high with a score of 7.3.

2

How do I fix CVE-2026-7818?

To fix CVE-2026-7818, you should apply the available patch for pgAdmin 4.

3

What kind of vulnerability is CVE-2026-7818?

CVE-2026-7818 is a vulnerability related to unsafe deserialization, specifically CWE-502.

4

What can be exploited through CVE-2026-7818?

CVE-2026-7818 can be exploited to achieve remote code execution.

5

Which component of pgAdmin 4 is affected by CVE-2026-7818?

The affected component in pgAdmin 4 is the FileBackedSessionManager.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203