HighCVE-2026-15741

    PostgreSQL expression deparse allows SQL injection via EXTRACT argument (CVE-2026-15741)

    Published Last modified Sources: Red Hat, Debian LTS, Ubuntu, Debian, SUSE, BSI, OSV, Msrc Update Guide, CVE.org

    What is affected, what to do

    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.

    Update PostgreSQL to version 16.15, PostgreSQL to version 15.19, PostgreSQL to version 14.24.

    Affected
    • PostgreSQL lt 16..16.15
    • PostgreSQL lt 15..15.19
    • PostgreSQL lt *..14.24
    • PostgreSQL lt 18..18.6
    • PostgreSQL lt 17..17.11
    Fixed in
    • PostgreSQL 16.15
    • PostgreSQL 15.19
    • PostgreSQL 14.24
    • PostgreSQL 18.6
    • PostgreSQL 17.11

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: Red Hat, Debian LTS, Ubuntu, Debian, SUSE, BSI, OSV, Msrc Update Guide, CVE.org

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 37.8

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    78.47 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    37.8
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 13 August 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-89

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: redhat_csaf, Debian LTS Advisories, Ubuntu Security Notices, Debian Security Advisories, suse_csaf, BSI WID Portal, BSI CSAF, OSV (Open Source Vulnerabilities), Microsoft Security Update Guide, cvelistv5, NVD (NIST)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    —PostgreSQL
    • < 14.24
    • 17 – < 17.11
    • 15 – < 15.19
    • 18 – < 18.6
    • 16 – < 16.15
    • 14.24
    • 17.11
    • 15.19
    • 18.6
    • 16.15
    postgresqlpostgresql
    • 14.0 – < 14.24
    • 17.0 – < 17.11
    • 16.0 – < 16.15
    • 18.0 – < 18.5
    • 15.0 – < 15.19
    • 14.24
    • 17.11
    • 16.15
    • 18.5
    • 15.19
    Open SourcePostgreSQL
    • < 14.24
    • <19 Beta 3
    • < 15.19
    • < 17.11
    • < 16.15
    • < 18.6
    • 14.24
    • —
    • 15.19
    • 17.11
    • 16.15
    • 18.6
    Distribution and container packages (4)

    Downstream packages (e.g. Bitnami, Debian, Ubuntu, Red Hat). Versions refer to the distribution, not the vendor.

    Distribution and container packages
    Affected versionsFixed in
    bitnamipostgresql
    • 18.0.0
    • 16.0.0
    • 17.0.0
    • 15.0.0
    • —
    • —
    • —
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianpostgresql-15bookworm
    Linuxdebianpostgresql-17trixie

    Weakness classes (CWE)

    • CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

      Base

      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.

      Entry at MITRE CWE-89

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedf86ef6dc…

      Description added or changed

      Show 5 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionchanged
      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.
      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.
      Affected versions (publisher)added
      —
      Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/15xxx/CVE-2026-15741.json">CVE-2026-15741</a>
      Referenceadded
      —
      https://www.postgresql.org/support/security/CVE-2026-15741/
      Referenceremoved
      https://www.postgresql.org/support/security/CVE-2026-15741/
      —
      Reference typeremoved
      https://www.postgresql.org/support/security/CVE-2026-15741/ Types: Vendor Advisory
      —

      Source identifier: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

    2. Initial analysis by NVDNVD

      Newly listed as affected:
      • PostgreSQL (14.0 – before 14.24; 15.0 – before 15.19; 16.0 – before 16.15; 17.0 – before 17.11; 18.0 – before 18.5)
      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Product configurationadded
      —
      OR *cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:* versions from (including) 14.0 up to (excluding) 14.24 *cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:* versions from (including) 15.0 up to (excluding) 15.19 *cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:* versions from (including) 16.0 up to (excluding) 16.15 *cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:* versions from (including) 17.0 up to (excluding) 17.11 *cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:* versions from (including) 18.0 up to (excluding) 18.5
      Reference typeadded
      —
      PostgreSQL: https://www.postgresql.org/support/security/CVE-2026-15741/ Types: Vendor Advisory

      Source identifier: nvd@nist.gov

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-15741
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-15741"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-15741.svg?lang=en" alt="CVE-2026-15741 – NEOSEC Intel" height="20"></a>