| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in pgAdmin 4 9.11. The impacted element is an unknown function of the component Web Interface. The manipulation leads to Remote Privilege Escalation. This vulnerability is traded as CVE-2026-1707. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability, which was classified as critical, has been found in pgAdmin 4 9.11. This issue affects some unknown functionality of the component Web Interface. The manipulation with an unknown input leads to a remote privilege escalation vulnerability. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-1707 since 01/30/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/27/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-5528). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.3
NVD Vector: 🔒
CNA Base Score: 7.4
CNA Vector (PostgreSQL): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Privilege escalationCWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
01/30/2026 CVE reserved02/05/2026 Advisory disclosed
02/05/2026 VulDB entry created
02/27/2026 VulDB entry last update
Sources
Advisory: 9518Status: Not defined
CVE: CVE-2026-1707 (🔒)
GCVE (CVE): GCVE-0-2026-1707
GCVE (VulDB): GCVE-100-344549
EUVD: 🔒
Entry
Created: 02/05/2026 20:09Updated: 02/27/2026 02:11
Changes: 02/05/2026 20:09 (60), 02/06/2026 06:34 (1), 02/06/2026 14:00 (1), 02/12/2026 20:27 (11), 02/27/2026 02:11 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.