Vulnerability in pgadmin4 (CVE-2026-1707)
Summary
Vulnerability in pgadmin4 (CVE-2026-1707). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 9.12 or later.
Original description
The description as published by the source.
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 . This results in reliable command execution on the pgAdmin host during the restore operation.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-1707 has been found in pgadmin4.
Risk of unauthorized operations or information disclosure.
What to do: upgrade pgadmin4 to 9.12 or later.
If unsure, ask your IT team or search "pgadmin4 CVE-2026-1707" on the vendor's site.
CVE-2026-1707 (pgadmin4) — CWE-284
Attack vector: remote (network-reachable) / no user interaction
Patched: 9.12 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in pgadmin4.
Check the vendor advisory for the affected versions of pgadmin4.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 9.12.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pgadmin4' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pgadmin4' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pgadmin4を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pgadmin4 to 9.12ステージング環境で 9.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com