Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-12046: Two state-mutating endpoints in pgAdmin 4's SQL Editor blueprint -- DELETE /sqleditor/close/<trans_id> and POS

52
This month
CRITICAL 9.0REMOTEUPGRADE

CVE-2026-12046 is a critical-severity flaw (CVSS 9.0) affecting pgadmin 4. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Two state-mutating endpoints in pgAdmin 4's SQL Editor blueprint -- DELETE /sqleditor/close/<trans_id> and POST /sqleditor/initialize/sqleditor/update_connection/<sgid>/<sid>/<did> -- were the only routes in the module missing the @pga_login_required decorator. Both reach a pickle.loads sink on session['gridData'][<trans_id>]['command_obj']: the close endpoint via close_sqleditor_session(), and update_sqleditor_connection via check_transaction_st

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.0 (Critical)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance1.0% (top 36%)
CISA exploited listNo
WeaknessCWE-306, CWE-502
Published2026-06-19
Last modified2026-10-25
Publisher (CNA): PostgreSQL · Vendor: pgadmin

Share: LinkedIn · X · Reddit

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

pgadmin pgadmin 4 UPGRADE
Affected: >= 6.9 and < 9.16
Fixed in: 9.16
Safe to downgrade to: a release before 6.9
1. Check installed version
apt-cache policy pgadmin-4 || rpm -q pgadmin-4 || pgadmin-4 --version
2. UPGRADE to 9.16 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade pgadmin-4
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade pgadmin-4
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 6.9 (Debian / Ubuntu)
apt-cache madison pgadmin-4 sudo apt install pgadmin-4=<VERSION_BEFORE_6.9> sudo apt-mark hold pgadmin-4
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list pgadmin-4 sudo dnf downgrade pgadmin-4-<VERSION_BEFORE_6.9> sudo dnf versionlock add pgadmin-4
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-12046?

pgadmin 4: upgrade to 9.16. Exact commands for each OS are on this page.

Is CVE-2026-12046 being exploited?

CVE-2026-12046 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-12046 affect?

CVE-2026-12046 affects pgadmin 4. Severity is critical (CVSS 9.0). Two state-mutating endpoints in pgAdmin 4's SQL Editor blueprint -- DELETE /sqleditor/close/<trans_id> and POST /sqleditor/initialize/sqleditor/update_connection/<sgid>/<sid>/<did> -- were the only routes in the module missing the @pga_logi

How urgent is CVE-2026-12046?

Priority 52/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.