dbcve.org
Pgadmin 4Application · Pgadmin

CVE-2026-1707

MEDIUM · 6.3 CVSS v3.1 Published 2026-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

pgAdmin 9.11 in server mode leaks the `\restrict` key through its web interface during PLAIN-format dump restores. An authenticated attacker monitoring an active restore can extract this key and win a race condition by overwriting the restore script with `\unrestrict <key>`, re-enabling disabled meta-commands and achieving arbitrary command execution on the pgAdmin host.

MitigationRestrict pgAdmin web interface access to trusted users only, monitor for unauthorized restore script modifications, and apply vendor patch when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pgadmin 4Application
Affected:= 9.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed pgAdmin version
    Check the pgAdmin version by logging into the web interface and viewing the 'About' page, or by checking the pgAdmin4 package/version file on the system (e.g., pip show pgadmin4 or rpm -qi pgadmin4)
    Affected if Version is exactly 9.11
  2. Confirm pgAdmin is running in server mode
    Verify the deployment mode by checking if pgAdmin is accessible via a web browser (indicating server mode). In server mode, pgAdmin runs as a WSGI application behind a web server. Check for process: python /path/to/pgAdmin4/py or equivalent web server configuration serving pgAdmin
    Affected if pgAdmin is accessible via HTTP/HTTPS in a web browser, confirming server mode operation
  3. Determine if PLAIN-format dumps are in use
    Review restore operations in pgAdmin by checking the backup/restore logs or by examining any active restore sessions in the web interface. PLAIN format dumps contain SQL statements that pgAdmin parses and executes during restore
    Affected if Plain-format PostgreSQL dumps (as opposed to custom or directory format) are being restored through pgAdmin's web interface
  4. Assess web interface exposure
    Check network accessibility of the pgAdmin web interface by reviewing firewall rules, reverse proxy configuration, and access control lists. Determine if the interface is exposed to untrusted networks
    Affected if The pgAdmin web interface is accessible from networks outside the trusted administrative zone, enabling unauthenticated or untrusted users to potentially observe restore operations

A user is affected if they are running pgAdmin version 9.11 in server mode and using the web interface to restore PLAIN-format dumps, with the interface accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict pgAdmin web interface access to trusted users only, monitor for unauthorized restore script modifications, and apply vendor patch when available.

Fix this in Pgadmin 4 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1707 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1707 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data