Is CVE-2026-12046 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-12046 being exploited in the wild.

How severe is CVE-2026-12046?

Critical severity, with a CVSS score of 9, published 19 June 2026.

Which products and versions are affected?

pgadmin.org pgAdmin 4 6.9 to 9.15.

Is there a fix for CVE-2026-12046?

A patch was published on 2026-06-19: Fixed in version 9.16 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-12046 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-12046?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-12046: pgAdmin 4 unauthenticated RCE in SQL Editor via pickle deserialization

CVE-2026-12046 · Severity: critical · CVSS 9 · Published 2026-06-19

pgAdmin 4 is a popular management tool for PostgreSQL databases. In certain server-mode configurations, two specific web endpoints were found to lack proper login requirements. If an attacker has already gained partial access to the server's configuration or files, they could use these unprotected endpoints to take full control of the pgAdmin application and the underlying server.

Quick answers

Is CVE-2026-12046 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-12046 being exploited in the wild.
How severe is CVE-2026-12046?: Critical severity, with a CVSS score of 9, published 19 June 2026.
Which products and versions are affected?: pgadmin.org pgAdmin 4 6.9 to 9.15.
Is there a fix for CVE-2026-12046?: A patch was published on 2026-06-19: Fixed in version 9.16 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-12046 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-12046?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

Two state-mutating endpoints in the SQL Editor blueprint—DELETE /sqleditor/close/<trans_id> and POST /sqleditor/initialize/sqleditor/update_connection/<sgid>/<sid>/<did>—missing the @pga_login_required decorator. This omission allows unauthenticated access in server mode to code paths that reach a pickle.loads() sink. While the vulnerability is a missing authentication check (CWE-306) leading to unsafe deserialization (CWE-502), successful exploitation for remote code execution (RCE) requires two significant preconditions: knowledge of the Flask SECRET_KEY and write access to the server's session directory. If these conditions are met via a separate vulnerability or misconfiguration, an attacker can achieve RCE as the user running the pgAdmin process. The issue is addressed in version 9.16 by adding the necessary authentication decorators.

Affected products

pgadmin.org pgAdmin 4 6.9 to 9.15

Timeline

2026-06-10: disclosed: Issue opened on GitHub
2026-06-19: advisory: NVD publication date
2026-06-19: patched: Fixed in version 9.16

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.