Security Digest · Vulnerability record
CVE-2025-12762: pgAdmin4 vulnerable to Remote Code Execution (RCE) when running in server mode
pgAdmin versions up to 9.9 are affected by a Remote Code Execution (RCE) vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files.
CVSS 9.1 Critical EPSS 12.7% · p96
Should you act?
High exploit likelihood
EPSS ranks it in the top 5% of all CVEs for likely exploitation in the next 30 days. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 12.7%, percentile 96: FIRST’s model estimates a 12.7% chance of exploitation activity in the next 30 days, higher than 96% of all scored CVEs (very high). EPSS is a probability, not a verdict.
- Needs an account (low (any account)). Exposure depends on who can log in.
- Only applies if your dependency tree includes
pgadmin4(PyPI) < 9.10, fixed in 9.10. Check your lockfile, including transitive dependencies.
What it is
pgAdmin versions up to 9.9 are affected by a Remote Code Execution (RCE) vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. This issue allows attackers to inject and execute arbitrary commands on the server hosting pgAdmin, posing a critical risk to the integrity and security of the database management system and underlying data.
From the GitHub advisory
pgAdmin versions up to 9.9 are affected by a Remote Code Execution (RCE) vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. This issue allows attackers to inject and execute arbitrary commands on the server hosting pgAdmin, posing a critical risk to the integrity and security of the database management system and underlying data.
Weakness type: CWE-94.
Product: pgadmin4 (PyPI) · Assigned by: PostgreSQL · Published: 2025-11-13
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | pgadmin4 | < 9.10 | 9.10 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| pgadmin.org | pgAdmin 4 | <= 9.9 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| PostgreSQL | 3.1 | 9.1 Critical | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: low (any account)
- User interaction: none
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable no, technical impact total.
- FIRST EPSS (model of 2026-10-21): 12.71% probability of exploitation activity in the next 30 days; percentile 96.
Timeline
- — CVE record published by PostgreSQL
- — GitHub-reviewed advisory GHSA-w2p4-p4rh-qcm3 published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-w2p4-p4rh-qcm3 github.com
- CVE.org record CVE-2025-12762 cve.org
- NVD entry CVE-2025-12762 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com