BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-15741High confidence

PostgreSQL expression deparse allows SQL injection via EXTRACT argument

n/a · PostgreSQL

8.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Mitigation available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivepostgresql-16Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.16.15-0ubuntu0.24.04.1Canonical record ↗Source updated 9 Sept 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-15741 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypostgresql: PostgreSQL: Privilege escalation via SQL injection in EXTRACT() deparse
186 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • postgresql as a component of Red Hat Enterprise Linux 10
  • postgresql-contrib as a component of Red Hat Enterprise Linux 10
  • postgresql-docs as a component of Red Hat Enterprise Linux 10
  • postgresql-plperl as a component of Red Hat Enterprise Linux 10
  • postgresql-plpython3 as a component of Red Hat Enterprise Linux 10
  • postgresql-pltcl as a component of Red Hat Enterprise Linux 10
  • postgresql-private-devel as a component of Red Hat Enterprise Linux 10
  • postgresql-private-libs as a component of Red Hat Enterprise Linux 10
  • postgresql-server as a component of Red Hat Enterprise Linux 10
  • postgresql-server-devel as a component of Red Hat Enterprise Linux 10
  • postgresql-static as a component of Red Hat Enterprise Linux 10
  • postgresql-test as a component of Red Hat Enterprise Linux 10
Summary
A SQL injection flaw in PostgreSQL's EXTRACT() expression deparser allows an authenticated object owner to execute arbitrary SQL commands with superuser privileges. 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.
Remediation
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,
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-57846

No EUVD known-exploited evidence

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.6, 17.11, 16.15, 15.19, and 14.24 are affected.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
8.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Mitigation available
01

What, why and how

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.6, 17.11, 16.15, 15.19, and 14.24 are affected.

What

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.6, 17.11, 16.15, 15.19, and 14.24 are affected.

Why

Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.6, 17.11, 16.15, 15.19, and 14.24 are affected.

Why

Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-89 ↗

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'). The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-89
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-57846Official EUVD mapping

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.6, 17.11, 16.15, 15.19, and 14.24 are affected.

Official EUVD record
BSI · German · WID-SEC-W-2026-2844PostgreSQL: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in PostgreSQL ausnutzen, um beliebigen Programmcode auszuführen, SQL-Injection-Angriffe durchzuführen, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren oder Denial-of-Service-Zustände herbeizuführen.

Official advisory
CERT-FR · French · CERTFR-2026-AVI-1024Multiples vulnérabilités dans PostgreSQL

d?id=CVE-2026-14671 Référence CVE CVE-2026-14672 https://www.cve.org/CVERecord?id=CVE-2026-14672 Référence CVE CVE-2026-14673 https://www.cve.org/CVERecord?id=CVE-2026-14673 Référence CVE CVE-2026-14676 https://www.cve.org/CVERecord?id=CVE-2026-14676 Référence CVE CVE-2026-14677 https://www.cve.org/CVERecord?id=CVE-2026-14677 Référence CVE CVE-2026-14678 https://www.cve.org/CVERecord?id=CVE-2026-14678 Référence CVE CVE-2026-14679 https://www.cve.org/CVERecord?id=CVE-2026-14679 Référence CVE CVE-2026-14680 https://www.cve.org/CVERecord?id=CVE-2026-14680 Référence CVE CVE-2026-14681 https://www.cve.org/CVERecord?id=CVE-2026-14681 Référence CVE CVE-2026-15741 https://www.cve.org/CVERecord?id=CVE-2026-15741 Référence CVE CVE-2026-15742 https://www.cve.org/CVERecord?id=CVE-2026-15742 Référence CVE CVE-2026-16238 https://www.cve.org/CVERecord?id=CVE-2026-16238 Référence CVE CVE-2026-16239 https://www.cve.org/CVERecord?id=CVE-2026-16239 Référence CVE CVE-2026-16241 https://www.cve.org/CVERecord?id=CVE-2026-16241 Référence CVE CVE-2026-18024 https://www.cve.org/CVERecord?id=CVE-2026-18024 Référence CVE CVE-2026-18408 https://www.cve.org/CVERecord?id=CVE-2026-18408 Référence CVE CVE-2026-19385 https://www.cve.org/CVERecord?id=CVE-2026-19385 Référence CVE CVE-2026-6464 https://www.cve.org/CVERecord?id=C

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Mitigation available
Affected
postgresql as a component of Red Hat Enterprise Linux 10; postgresql-contrib as a component of Red Hat Enterprise Linux 10; postgresql-docs as a component of Red Hat Enterprise Linux 10; postgresql-plperl as a component of Red Hat Enterprise Linux 10; postgresql-plpython3 as a component of Red Hat Enterprise Linux 10; postgresql-pltcl as a component of Red Hat Enterprise Linux 10; postgresql-private-devel as a component of Red Hat Enterprise Linux 10; postgresql-private-libs as a component of Red Hat Enterprise Linux 10; postgresql-server as a component of Red Hat Enterprise Linux 10; postgresql-server-devel as a component of Red Hat Enterprise Linux 10; postgresql-static as a component of Red Hat Enterprise Linux 10; postgresql-test as a component of Red Hat Enterprise Linux 10; postgresql-test-rpm-macros as a component of Red Hat Enterprise Linux 10; postgresql-upgrade as a component of Red Hat Enterprise Linux 10; postgresql-upgrade-devel as a component of Red Hat Enterprise Linux 10; postgresql16.src as a component of Red Hat Enterprise Linux 10; postgresql18 as a component of Red Hat Enterprise Linux 10; postgresql18-contrib as a component of Red Hat Enterprise Linux 10; postgresql18-docs as a component of Red Hat Enterprise Linux 10; postgresql18-plperl as a component of Red Hat Enterprise Linux 10; postgresql18-plpython3 as a component of Red Hat Enterprise Linux 10; postgresql18-private-devel as a component of Red Hat Enterprise Linux 10; postgresql18-private-libs as a component of Red Hat Enterprise Linux 10; postgresql18-server as a component of Red Hat Enterprise Linux 10; postgresql18-server-devel as a component of Red Hat Enterprise Linux 10; postgresql18-static as a component of Red Hat Enterprise Linux 10; postgresql18-test as a component of Red Hat Enterprise Linux 10; postgresql18-test-rpm-macros as a component of Red Hat Enterprise Linux 10; postgresql18-upgrade as a component of Red Hat Enterprise Linux 10; postgresql18-upgrade-devel as a component of Red Hat Enterprise Linux 10; and 156 more
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
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,
04

Evidence and provenance

Published 13 Aug 2026 · Last source change 29 Aug 2026, 23:07 UTC · CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-57846
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    18 < 18.5; 17 < 17.11; 16 < 16.15; 15 < 15.19; < 14.24 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    18 < 18.6; 17 < 17.11; 16 < 16.15; 15 < 15.19; < 14.24 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from no authoritative guidance recorded to vendor advisory.
    Before
    no authoritative guidance recorded
    After
    vendor advisory
    f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2026-57846↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-15741 · cve.blacktree.nl