Restore restriction bypass via key disclosure vulnerability (pgAdmin 4)

published 2026-02-05 9 mo ago modified 2026-07-13 3 mo ago also GHSA-3p7x-94q9-jq9x , PYSEC-2026-2864 , EUVD-2026-5528

cvss: 7.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits: 0; none known

pgAdmin versions 9.11 are affected by a Restore restriction bypass via key disclosure vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. An attacker with access to the pgAdmin web interface can observe an active restore operation, extract the `\restrict` key in real time, and race the restore process by overwriting the restore script with a payload that re-enables meta-commands using `\unrestrict <key>`. This results in reliable command execution on the pgAdmin host during the restore operation.

Patch / fix

fixed in 1 distros 1 links 1

pypi pgadmin4 9.12

pgadmin4 openSUSE Tumbleweed 9.17-1.1

opensuse advisories openSUSE-SU-2026:11508-1

github.com/pgadmin-org/pgadmin4@62e2d18 commit

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-1707 updated 2026-06-28 cvss 8.5

pgadmin4: restore restriction bypass via key disclosure vulnerability

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 9 mo ago (2026-02-06)

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
NVD	3.1	6.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
GitHub	3.1	7.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
OSV	3.1	7.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Affected packages

ecosystem	package	affected	fixed in
pypi	pgadmin4	<9.12	9.12

Affected products

pgadmin.org pgAdmin 4

Classification

Weakness

CWE-284 Improper Access Control
CWE-639 Authorization Bypass Through User-Controlled Key

References

github.com /pgadmin-org/pgadmin4/commit/62e2d18b0261f88086db65059a6078db07169f18
web
github.com /pgadmin-org/pgadmin4/issues/9518
issue-tracking, web
nvd.nist.gov /vuln/detail/CVE-2026-1707
advisory
github.com /pgadmin-org/pgadmin4
package
pypi.org /project/pgadmin4
package
github.com /advisories/GHSA-3p7x-94q9-jq9x
advisory

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary