Categories
CVE-2026-12046 critical CVSS 9.0

Vulnerability in Pgadmin (CVE-2026-12046)

Summary

Vulnerability in Pgadmin (CVE-2026-12046). Successful exploitation can lead to full system takeover. Exploitable via DELETE /sqleditor/close/.

Original description

The description as published by the source.

Two state-mutating endpoints in pgAdmin 4's SQL Editor blueprint -- DELETE /sqleditor/close/ and POST /sqleditor/initialize/sqleditor/update_connection/// -- were the only routes in the module missing the @pga_login_required decorator. Both reach a pickle.loads sink on session['gridData'][]['command_obj']: the close endpoint via close_sqleditor_session(), and update_sqleditor_connection via check_transaction_status(). In server mode these endpoints were reachable without any authenticated pgAdmin session.

The defect is a missing-authentication-on-critical-function (CWE-306) wrapper around a deserialization-of-untrusted-data sink (CWE-502). Exploiting it for remote code execution requires the attacker to also forge a server-side session file whose gridData entry contains a malicious pickle payload, which in turn requires both (a) knowledge of pgAdmin's Flask SECRET_KEY (no chain to leak it is described here -- the attacker must already possess it) and (b) write access to pgAdmin's sessions/ directory on the host. Neither precondition is granted by this defect on its own. When those preconditions are met from another channel (misconfigured deployment, prior compromise, leaked configuration), the missing auth gate is the final hop that turns an existing partial compromise into unauthenticated code execution in the pgAdmin process -- and, by extension, on the host under whatever account runs pgAdmin.

Fix is a one-line @pga_login_required decorator on each of the two endpoints,…

Source: GitHub Security Advisories (Global) 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-2026-12046 has been found in Pgadmin.
Attackers can target a specific entry point like DELETE /sqleditor/close/ over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Pgadmin CVE-2026-12046" on the vendor's site.

CVE-2026-12046 (Pgadmin) — CWE-306 / CVSS v3 9.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DELETE /sqleditor/close/ / POST /sqleditor/initialize/sqleditor/update_connection/ / GET /login
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.

❓ What is the problem

A vulnerability (CWE-306) exists in Pgadmin. Attackers reach the vulnerable code path via DELETE /sqleditor/close/ without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Pgadmin. Attack surface: DELETE /sqleditor/close/ / POST /sqleditor/initialize/sqleditor/update_connection/ / GET /login.

🔥 Severity

Severity: Critical (CVSS 9.0/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual DELETE /sqleditor/close/ requests with malformed payloads or SQL meta-characters. Run grep -r 'Pgadmin' . 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

  1. 1
    Identify exposure identify
    grep -r 'Pgadmin' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Pgadmin を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'DELETE /sqleditor/close/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで DELETE /sqleditor/close/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify
    Replay attack against DELETE /sqleditor/close/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details