Quick answers
- Is CVE-2026-6473 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6473 being exploited in the wild.
- How severe is CVE-2026-6473?
- High severity, with a CVSS score of 8.8, published 14 May 2026.
- Which products and versions are affected?
- PostgreSQL Global Development Group PostgreSQL < 18.4, < 17.10, < 16.14, < 15.18, < 14.23.
- Is there a fix for CVE-2026-6473?
- A patch was published on 2026-05-12: Fixes released in multiple branches. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-6473 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-6473?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An integer wraparound vulnerability (CWE-190) exists within multiple core server features of PostgreSQL. By providing gigabyte-scale inputs to specific database functions, an authenticated but unprivileged user can trigger an integer overflow that results in an undersized memory allocation. This leads to an out-of-bounds write, which can cause a segmentation fault (DoS) or potentially allow arbitrary code execution with the privileges of the operating system user running the PostgreSQL service. The vulnerability is reachable over the network but requires valid database credentials. Patches are available in versions 18.4, 17.10, 16.14, 15.18, and 14.23.
Affected products
- PostgreSQL Global Development Group PostgreSQL < 18.4, < 17.10, < 16.14, < 15.18, < 14.23
Timeline
- 2026-05-12: patched: Fixes released in multiple branches.
- 2026-05-14: disclosed: Public advisory published.