LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1707: Restore restriction bypass via key disclosure vulnerability (pgAdmin 4)

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.

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-1707 affects pgAdmin 4 version 9.11 in server mode during restores from PLAIN-format dump files. A logged-in attacker with pgAdmin web access can interfere with an active restore and cause command execution on the pgAdmin host. Treat this as high priority where pgAdmin server mode is used by multiple users or exposed beyond trusted administrators.

Executive priority

Prioritize remediation for shared or network-accessible pgAdmin 9.11 servers, especially where database restores are routine. The business risk is host-level command execution from an authenticated web user during restore activity. If pgAdmin is limited to trusted administrators and no PLAIN restores occur, urgency is lower but still requires vendor tracking.

Technical view

The issue is a restore restriction bypass via disclosure of a restore restriction key during active PLAIN-format restores. With pgAdmin web-interface access, an attacker can observe the restore process and race modification of the restore script so restricted meta-commands are re-enabled, leading to command execution on the pgAdmin host. The CVE assigns CVSS 7.4, CWE-284, affecting pgAdmin 4 9.11.

Likely exposure

Exposure is limited to pgAdmin 4 version 9.11 running in server mode, where an attacker has authenticated access to the pgAdmin web interface and can observe active PLAIN-format restore operations. Single-user desktop deployments or environments not using PLAIN-format restores appear less exposed based on the provided description.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not state active exploitation in the wild. Exploitation requires pgAdmin web access and timing around an active restore, but the source description characterizes command execution as reliable once those conditions are met.

Researcher notes

Evidence is currently limited to the CVE metadata and pgAdmin GitHub issue reference. No patch version, workaround, or exploitation-in-the-wild claim is present in the provided sources. Validation should focus on version, server mode, restore workflow, and access control boundaries rather than assuming all pgAdmin installations are affected.

Mitigation direction

  • Check pgAdmin issue 9518 and vendor advisories for an official fix or workaround.
  • Restrict pgAdmin web access to trusted administrators only.
  • Avoid or tightly control PLAIN-format restores in server mode until guidance is available.
  • Limit who can start, view, or manage restore operations in pgAdmin.
  • Review pgAdmin host privileges to reduce impact of command execution.

Validation and detection

  • Inventory pgAdmin deployments and identify any version 9.11 instances.
  • Confirm whether affected instances run in server mode.
  • Determine whether PLAIN-format dump restores are performed through pgAdmin.
  • Review pgAdmin user access for non-administrative or broadly shared accounts.
  • Monitor logs around restore operations for unexpected activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1707 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L3.13.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2026-1707Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
pgadmin.orgpgAdmin 49.11unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.