CVE-2026-6473

PostgreSQL server undersizes allocations, via integer wraparound

HIGH

8.8

CVSS Score

Published: May 14, 2026 at 01:00 PM UTC

Updated: August 25, 2026 at 01:40 PM UTC

1 product affected across 1 vendorPostgreSQL

Using PostgreSQL by N/A?

Get instant alerts when new vulnerabilities affect PostgreSQL - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH8.8

Exploit prediction

EPSS 1%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

PostgreSQL · PostgreSQL

95%

v < 14.2315 ≤ v < 15.1815.0 ≤ v < 15.1816 ≤ v < 16.1416.0 ≤ v < 16.1417 ≤ v < 17.1017.0 ≤ v < 17.1018 ≤ v < 18.418.0 ≤ v < 18.415 16 17 18

Affected range stops below 14.23, so it looks safe — our inference, not a vendor statement

Affected range stops below 15.18, so it looks safe — our inference, not a vendor statement

Affected range stops below 16.14, so it looks safe — our inference, not a vendor statement

Affected range stops below 17.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://www.postgresql.org/support/security/CVE-2026-6473/