CVE-2026-12044
SQLi in pgAdmin 4 via user-provided description in several templates.
Is CVE-2026-12044 being exploited?
Not confirmed. CVE-2026-12044 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 0.71% probability of exploitation in the next 30 days.
How severe is CVE-2026-12044?
CVE-2026-12044 is rated High with a CVSS score of 8.7. 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-12044?
Yes. A fix has been recorded for CVE-2026-12044. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-12044 affect?
CVE-2026-12044 affects pgAdmin 4 (pre-9.16). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-12044?
Update to pgAdmin 4 v9.16+; review templates for injections.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated pgAdmin user can inject SQL; could lead to OS commands if privileged, bypassing app gates.
Patch when possible
- affected>= 1.0 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.