High [CVE-2026-15741] Privilege escalation via SQL injection in EXTRACT deparse
This high-severity Red Hat Linux advisory covers CVE-2026-15741 affecting Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
SQL injection in PostgreSQL EXTRACT() deparse allows an object owner to execute arbitrary SQL as a superuser via a hostile object definition. Attacks affect expression deparse consumers broadly, including pg_dump, psql commands like \sf, and any similar usage in non-core tools.
Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. By defining a hostile database object, an attacker can achieve privilege escalation when deparsing tools like pg_dump or psql inspect or export the object.
This poses a significant risk to environments where non-administrative users are granted object creation rights. Red Hat severity: Important — CVSS 8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H).
Weakness: CWE-89.
Affected products named by the advisory: Red Hat Enterprise Linux 10.0 Extended Update Support; Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support; Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On; Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support; and 11 more.
- < 18.5
- < 17.11
- < 16.15
- < 15.19
- < 14.24
Official advisory · high-confidence parse· fetched 15 days ago·verify at source
- postgresql18-0:18.6-1.el10_2
- postgresql16-0:16.15-1.el10_2
- postgresql16-0:16.15-1.el10_0
- postgresql:16-8100020260910192321.489197e6
- postgresql:15-8100020260906175012.489197e6
- postgresql:12-8040020260924163759.522a0ee4
- postgresql:12-8060020260923144955.ad008a3a
- postgresql:15-8080020260921162003.63b34585
- postgresql:12-8080020260923144922.63b34585
- postgresql:16-9080020260907191505.rhel9
- postgresql:18-9080020260914093252.rhel9
- postgresql:15-9080020260903073937.rhel9
- postgresql:15-9020020260917092006.rhel9
- postgresql:15-9040020260917091622.rhel9
- postgresql:16-9040020260922062609.rhel9
- postgresql:16-9060020260921091101.rhel9
- ansible-automation-platform/bootc-automation-portal-rhel9:1790657374
- rhui5/rhua-rhel9:1790242004
- RHSA-2026:67280
- RHSA-2026:70186
- RHSA-2026:72282
- RHSA-2026:69876
- RHSA-2026:69923
- RHSA-2026:73912
- RHSA-2026:72363
- RHSA-2026:70602
- RHSA-2026:72362
- RHSA-2026:67491
- RHSA-2026:67848
- RHSA-2026:69914
- RHSA-2026:70763
- RHSA-2026:70762
- RHSA-2026:70856
- RHSA-2026:70559
- RHSA-2026:73404
- RHSA-2026:71603
Official advisory · high-confidence parse· fetched 15 days ago·verify at source
Mitigation checklist
- To mitigate this vulnerability, administrators should strictly limit database object creation privileges to highly trusted users. When performing backups or database introspection using pg_dump or psql, exercise caution when operating on databases that allow untrusted users to define objects,
Official advisory · high-confidence parse· fetched 15 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.