Quick answers
- Is CVE-2026-6637 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6637 being exploited in the wild.
- How severe is CVE-2026-6637?
- High severity, with a CVSS score of 8.8, published 14 May 2026.
- Which products and versions are affected?
- PostgreSQL Before 18.4, 17.10, 16.14, 15.18, and 14.23.
- Is there a fix for CVE-2026-6637?
- 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-6637 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-6637?
- Check whether you run PostgreSQL at an affected version. 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
The PostgreSQL 'refint' module contains a stack-based buffer overflow (CWE-121) and is susceptible to SQL injection (CWE-89). An unprivileged database user can exploit the buffer overflow to execute arbitrary code with the privileges of the operating system user running the PostgreSQL service. Furthermore, if an application uses a user-controlled column as a 'refint' cascade primary key, an attacker can use SQL injection to execute arbitrary SQL commands with the privileges of the user performing the update. These issues are resolved in PostgreSQL versions 18.4, 17.10, 16.14, 15.18, and 14.23.
Affected products
- PostgreSQL PostgreSQL Before 18.4, 17.10, 16.14, 15.18, and 14.23
Timeline
- 2026-05-12: patched: Fixes released in multiple branches.
- 2026-05-14: disclosed: Public advisory published.