PostgreSQL is widely used; this flaw allows object owners to run arbitrary SQL as superuser, risking full DB compromise across many deployments.
CVE-2026-15741
SQL injection in PostgreSQL EXTRACT() deparse enables arbitrary superuser SQL execution.
WAF coverage: SQL injection. Signatures match well at the request layer.
Also consider: parameterized queries · ORM
Is CVE-2026-15741 being exploited?
Not confirmed. CVE-2026-15741 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.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-15741?
CVE-2026-15741 is rated High with a CVSS score of 8.8. 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-15741?
Yes. A fix has been recorded for CVE-2026-15741. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15741 affect?
CVE-2026-15741 affects PostgreSQL versions before 18.5, PostgreSQL versions before 17.11, PostgreSQL versions before 16.15, PostgreSQL versions before 15.19, and 4 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15741?
Upgrade to PostgreSQL 18.5/17.11/16.15/15.19/14.24 and avoid loading untrusted object definitions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Object owners can execute arbitrary SQL as superuser via hostile object definitions, enabling data theft, privilege escalation, and full DB compromise.
Immediate action required
- affected>= 18 and < 18.6
- affected>= 17 and < 17.11
- affected>= 16 and < 16.15
- affected>= 15 and < 15.19
- affected< 14.24
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.