CVE-2026-19385: PostgreSQL pg_dump heap buffer overflow executes arbitrary code

Published Aug 13, 2026
·
Updated

Heap buffer overflow in PostgreSQL pgdump of long function transform lists allows an object creator to execute arbitrary code as the operating system user running pgdump, via a crafted transform list. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

Other sources

PostgreSQL pgdump heap buffer overflow executes arbitrary code

— Microsoft

Affected Software

21 affected componentsFixes available
PostgreSQL pg_dump<18.5, <17.11, <16.15, <15.19, <14.24
Microsoft azl3 postgresql 16.14-1<16.15-1
16.15-1
PostgreSQL postgresql>=14.0<14.24
PostgreSQL postgresql>=15.0<15.19
PostgreSQL postgresql>=16.0<16.15
PostgreSQL postgresql>=17.0<17.11
PostgreSQL postgresql>=18.0<18.5
IBM QRadar<=7.6.0.0 - 7.6.0.4
IBM QRadar<=7.5.0 - 7.5.0 UP16 IF01
alpine/postgresql15<15.19-r0
15.19-r0
alpine/postgresql15<15.19-r0
15.19-r0
alpine/postgresql16<16.15-r0
16.15-r0
alpine/postgresql16<16.15-r0
16.15-r0
alpine/postgresql16<16.15-r0
16.15-r0
alpine/postgresql16<16.15-r0
16.15-r0
alpine/postgresql17<17.11-r0
17.11-r0
alpine/postgresql17<17.11-r0
17.11-r0
alpine/postgresql17<17.11-r0
17.11-r0
alpine/postgresql17<17.11-r0
17.11-r0
alpine/postgresql18<18.5-r0
18.5-r0
alpine/postgresql18<18.5-r0
18.5-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.15-1
  2. Upgrade

    Upgrade alpine/postgresql15 to a version that resolves this vulnerability.

    Fixed in 15.19-r0
  3. Upgrade

    Upgrade alpine/postgresql16 to a version that resolves this vulnerability.

    Fixed in 16.15-r0
  4. Upgrade

    Upgrade alpine/postgresql17 to a version that resolves this vulnerability.

    Fixed in 17.11-r0
  5. Upgrade

    Upgrade alpine/postgresql18 to a version that resolves this vulnerability.

    Fixed in 18.5-r0
  6. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 18.6
  7. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 17.11
  8. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 16.15
  9. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 15.19
  10. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 14.24

Event History

Aug 13, 2026
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:17 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·01:17 PM
DescriptionSeverityAffected Software
Data Sourced
via Red Hat·01:31 PM
DescriptionSeverityAffected Software
Aug 15, 2026
Data Sourced
via Microsoft·02:24 AM
DescriptionSeverityWeaknessAffected Software
Oct 13, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-19385?

The severity of CVE-2026-19385 is high, with a score of 8.8.

2

How do I fix CVE-2026-19385?

To fix CVE-2026-19385, you should upgrade to PostgreSQL versions 18.5, 17.11, 16.15, 15.19, or 14.24 or later.

3

What type of vulnerability is CVE-2026-19385?

CVE-2026-19385 is a heap buffer overflow vulnerability.

4

What impact does CVE-2026-19385 have on PostgreSQL pg_dump?

CVE-2026-19385 allows an object creator to execute arbitrary code as the operating system user running pg_dump.

5

Which versions of PostgreSQL are affected by CVE-2026-19385?

PostgreSQL versions prior to 18.5, 17.11, 16.15, 15.19, and 14.24 are affected by CVE-2026-19385.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203