Code Injection in pgadmin4 (CVE-2025-12762)
Summary
Code injection in pgadmin4 (CVE-2025-12762). Confidential information can be exposed externally. Mitigation: upgrade to 9.10 or later.
Original description
The description as published by the source.
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.
Source: JVN (Japan Vulnerability Notes) NVD GitHub Advisory
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-2025-12762 has been found in pgadmin4.
Confidential information can be exposed externally.
What to do: upgrade pgadmin4 to 9.10 or later.
If unsure, ask your IT team or search "pgadmin4 CVE-2025-12762" on the vendor's site.
CVE-2025-12762 (pgadmin4) — CWE-94
Attack vector: remote (network-reachable) / no user interaction
Patched: 9.10 — 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.
Arbitrary code execution (CWE-94) exists in pgadmin4.
Check the vendor advisory for the affected versions of pgadmin4.
Severity: ?. Confidential information can be exposed externally.
Update to 9.10.
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.10ステージング環境で 9.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- JVN JVNDB-2026-027059
- package github.com
- package pypi.org
- report github.com
- web github.com