Unsafe Deserialization in pgAdmin Session Management

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 419matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-7818 exploits unsafe deserialization of session files in pgAdmin 4's FileBackedSessionManager, allowing arbitrary code execution through malicious serialized Python objects. The vulnerability stems from deserializing untrusted session data using Python's pickle module before performing any integrity verification. This affects pgAdmin administrators and users in environments where an authenticated attacker gains write access to the sessions directory—either through misconfiguration or combined with path-traversal exploits. With a CVSS score of 7.0, this represents a high-severity risk that could lead to complete system compromise.

Casky.ai's 419 mapped skills detect the attack patterns behind this vulnerability by analyzing initial access (TA0001), persistence (TA0043), and execution (TA0002) techniques. Practitioners using Casky would observe findings revealing unauthorized file writes to session directories, suspicious deserialization calls on untrusted input, and execution of unexpected Python objects loaded from session files. Claude's extended reasoning capabilities help correlate defensive indicators across the attack chain—from identifying write-access misconfigurations that enable initial file placement, to detecting the deserialization gadget chains that trigger code execution—enabling security teams to identify both the vulnerability and its exploitation in their pgAdmin deployments.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

419 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-7818.

analyzing-android-malware-with-apktool

malware analysis · medium

Run

analyzing-apt-group-with-mitre-navigator

threat intelligence · low

Run

analyzing-bootkit-and-rootkit-samples

malware analysis · medium

Run

MITRE ATT&CK Techniques

TA0001 TA0043 TA0002

Investigate the attack patterns behind CVE-2026-7818

Casky has 419 skills that investigate the attack patterns behind CVE-2026-7818. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn