CVE-2026-6473: PostgreSQL server undersizes allocations, via integer wraparound

Published May 14, 2026
·
Updated

Integer wraparound in multiple PostgreSQL server features allows an unprivileged database user to cause the server to undersize an allocation and write out-of-bounds. This may execute arbitrary code as the operating system user running the database. In applications that pass gigabyte-scale user inputs to the relevant database functions, the application input provider may achieve a segmentation fault. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

Other sources

PostgreSQL server undersizes allocations, via integer wraparound

Microsoft

Affected Software

11 affected componentsFixes available
PostgreSQL postgresql<18.4, <17.10, <16.14, <15.18, <14.23
Microsoft azl3 postgresql 16.12-1
PostgreSQL postgresql<14.23
PostgreSQL postgresql>=15.0<15.18
PostgreSQL postgresql>=16.0<16.14
PostgreSQL postgresql>=17.0<17.10
PostgreSQL postgresql>=18.0<18.4
debian/postgresql-13<=13.16-0+deb11u1, <=13.23-0+deb11u3
debian/postgresql-15<=15.17-0+deb12u1
15.18-0+deb12u1
debian/postgresql-17<=17.9-0+deb13u1
17.10-0+deb13u1
debian/postgresql-18
18.4-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/postgresql-15 to a version that resolves this vulnerability.

    Fixed in 15.18-0+deb12u1
  2. Upgrade

    Upgrade debian/postgresql-17 to a version that resolves this vulnerability.

    Fixed in 17.10-0+deb13u1
  3. Upgrade

    Upgrade debian/postgresql-18 to a version that resolves this vulnerability.

    Fixed in 18.4-1
  4. Upgrade

    Upgrade PostgreSQL server to a version that resolves this vulnerability.

    Fixed in 18.4
  5. Upgrade

    Upgrade PostgreSQL server to a version that resolves this vulnerability.

    Fixed in 17.10
  6. Upgrade

    Upgrade PostgreSQL server to a version that resolves this vulnerability.

    Fixed in 16.14
  7. Upgrade

    Upgrade PostgreSQL server to a version that resolves this vulnerability.

    Fixed in 15.18
  8. Upgrade

    Upgrade PostgreSQL server to a version that resolves this vulnerability.

    Fixed in 14.23

Event History

May 14, 2026
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·02:02 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 16, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:04 AM
DescriptionSeverity
May 21, 2026
Data Sourced
via Launchpad·10:49 PM
Description
May 22, 2026
Data Sourced
via Ubuntu·10:49 PM
RemedyDescriptionSeverityAffected Software
May 25, 2026
Data Sourced
via Debian·10:55 PM
DescriptionAffected Software
Aug 5, 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-6473?

CVE-2026-6473 is considered a critical vulnerability due to its potential to allow arbitrary code execution.

2

How do I fix CVE-2026-6473?

To mitigate CVE-2026-6473, upgrade PostgreSQL to version 14.24 or later, 15.19 or later, 16.15 or later, 17.11 or later, or 18.5 or later.

3

What systems are affected by CVE-2026-6473?

CVE-2026-6473 affects various versions of PostgreSQL including versions before 14.24, 15.19, 16.15, 17.11, and 18.5.

4

Who can exploit CVE-2026-6473?

An unprivileged database user can exploit CVE-2026-6473 to cause the PostgreSQL server to undersize allocations.

5

What are the implications of CVE-2026-6473?

Exploitation of CVE-2026-6473 can lead to out-of-bounds writes and potential execution of arbitrary code by the operating system user running PostgreSQL.

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