Widely-used pgAdmin admin tool; unauthenticated RCE in server mode could affect orgs globally.
CVE-2026-12046
Unauthenticated RCE in pgAdmin 4 server mode via missing auth on SQL Editor endpoints.
Is CVE-2026-12046 being exploited?
Not confirmed. CVE-2026-12046 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.0% probability of exploitation in the next 30 days.
How severe is CVE-2026-12046?
CVE-2026-12046 is rated Critical with a CVSS score of 9.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-12046?
Yes. A fix has been recorded for CVE-2026-12046. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-12046 affect?
CVE-2026-12046 affects pgAdmin 4 (6.9–9.15). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-12046?
Upgrade to pgAdmin 4 >= 9.16
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution on the pgAdmin server via two endpoints; requires forged session, Flask SECRET_KEY, and session-file write access (server mode only).
Patch when possible
- affected>= 6.9 and < 9.16
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.