CVE-2026-7818

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.0
EG Score
7.0(medium)
EPSS
3.1%
KEV
Not listed

Published

May 11, 2026

Last Modified

May 26, 2026

Advisory Details (1)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

Unsafe deserialization in file-backed session manager leads to RCE (CVE-2026-7818) · Issue #9901 · pgadmin-org/pgadmin4 · GitHub

https://github.com/pgadmin-org/pgadmin4/issues/9901

Vendor Advisories for CVE-2026-7818(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pgadmin44.20 ... 9.9 (77 versions)9.15—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-08 15:16 UTCEPSS rescore
  6. 2026-07-07 13:46 UTCEPSS rescore
  7. 2026-07-07 13:46 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 16:27 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 03:25 UTCEG score recompute
  20. 2026-06-27 09:54 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 21:07 UTCEG score recompute
  23. 2026-06-26 05:09 UTCEG score recompute
  24. 2026-06-25 13:50 UTCEPSS rescore
  25. 2026-06-24 14:05 UTCEPSS rescore
Show 69 more
  1. 2026-06-23 21:33 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-21 14:56 UTCEPSS rescore
  4. 2026-06-21 01:59 UTCEPSS rescore
  5. 2026-06-19 19:26 UTCEPSS rescore
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-17 17:53 UTCEPSS rescore
  8. 2026-06-17 01:03 UTCEG score recompute
  9. 2026-06-16 17:53 UTCEPSS rescore
  10. 2026-06-16 07:28 UTCEG score recompute
  11. 2026-06-15 17:49 UTCEPSS rescore
  12. 2026-06-15 17:49 UTCEPSS rescore
  13. 2026-06-15 02:10 UTCEG score recompute
  14. 2026-06-14 23:18 UTCEPSS rescore
  15. 2026-06-14 14:35 UTCEG score recompute
  16. 2026-06-14 01:57 UTCEG score recompute
  17. 2026-06-13 23:00 UTCEPSS rescore
  18. 2026-06-13 08:23 UTCEG score recompute
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-06-12 23:12 UTCEPSS rescore
  21. 2026-06-12 20:18 UTCEG score recompute
  22. 2026-06-12 08:45 UTCEG score recompute
  23. 2026-06-11 21:12 UTCEG score recompute
  24. 2026-06-11 14:00 UTCEPSS rescore
  25. 2026-06-11 09:39 UTCEG score recompute
  26. 2026-06-10 22:19 UTCEPSS rescore
  27. 2026-06-10 22:06 UTCEG score recompute
  28. 2026-06-10 13:22 UTCEPSS rescore
  29. 2026-06-10 10:34 UTCEG score recompute
  30. 2026-06-09 23:00 UTCEG score recompute
  31. 2026-06-09 11:28 UTCEG score recompute
  32. 2026-06-08 23:55 UTCEG score recompute
  33. 2026-06-08 14:17 UTCEPSS rescore
  34. 2026-06-08 12:22 UTCEG score recompute
  35. 2026-06-08 00:50 UTCEG score recompute
  36. 2026-06-07 15:25 UTCEPSS rescore
  37. 2026-06-07 13:17 UTCEG score recompute
  38. 2026-06-07 01:42 UTCEG score recompute
  39. 2026-06-06 14:09 UTCEG score recompute
  40. 2026-06-06 13:47 UTCEPSS rescore
  41. 2026-06-06 02:36 UTCEG score recompute
  42. 2026-06-05 22:47 UTCEPSS rescore
  43. 2026-06-05 15:03 UTCEG score recompute
  44. 2026-06-05 06:10 UTCEPSS rescore
  45. 2026-06-05 03:30 UTCEG score recompute
  46. 2026-06-04 15:57 UTCEG score recompute
  47. 2026-06-04 13:12 UTCEPSS rescore
  48. 2026-06-04 04:24 UTCEG score recompute
  49. 2026-06-03 16:51 UTCEG score recompute
  50. 2026-06-03 05:18 UTCEG score recompute
  51. 2026-06-02 20:13 UTCEPSS rescore
  52. 2026-06-02 17:45 UTCEG score recompute
  53. 2026-06-02 06:12 UTCEG score recompute
  54. 2026-06-01 18:38 UTCEG score recompute
  55. 2026-06-01 13:52 UTCEPSS rescore
  56. 2026-06-01 07:05 UTCEG score recompute
  57. 2026-05-31 22:30 UTCEPSS rescore
  58. 2026-05-31 00:16 UTCEPSS rescore
  59. 2026-05-29 13:44 UTCEPSS rescore
  60. 2026-05-28 13:44 UTCEPSS rescore
  61. 2026-05-27 13:40 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-26 13:44 UTCEPSS rescore
  64. 2026-05-26 07:18 UTCEPSS rescore
  65. 2026-05-23 00:07 UTCEG score recompute
  66. 2026-05-21 22:43 UTCEPSS rescore
  67. 2026-05-20 22:38 UTCEPSS rescore
  68. 2026-05-20 13:18 UTCEG score recompute
  69. 2026-05-20 11:22 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-7818?
CVE-2026-7818 is a high vulnerability published on May 11, 2026. 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…
When was CVE-2026-7818 disclosed?
CVE-2026-7818 was first published in the National Vulnerability Database on May 11, 2026, with the most recent update on May 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7818 actively exploited?
CVE-2026-7818 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7818?
CVE-2026-7818 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-7818?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7818, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-7818

Explore →

Is Your Infrastructure Affected by CVE-2026-7818?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs