Quick answers
- Is CVE-2026-120151 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120151 being exploited in the wild.
- How severe is CVE-2026-120151?
- High severity, with a CVSS score of 8.8, published 12 November 2026.
- Which products and versions are affected?
- PostgreSQL Before 14.25, 15.20, 16.16, 17.12, and 18.7.
- Is there a fix for CVE-2026-120151?
- Yes: fixed in PostgreSQL 14.25, 15.20, 16.16, 17.12, 18.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120151 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-120151?
- 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.
How to fix
- Fixed in: PostgreSQL 14.25, 15.20, 16.16, 17.12, 18.7
Technical details
A type confusion flaw in plpgsql record-field assignment allows privilege escalation to arbitrary code execution when a reentrant domain CHECK constraint changes a RECORD variable's row type during value casting. This requires an authenticated attacker with object creation privileges. Fixes are available in PostgreSQL 14.25, 15.20, 16.16, 17.12, and 18.7.
Affected products
- PostgreSQL PostgreSQL Before 14.25, 15.20, 16.16, 17.12, and 18.7
Timeline
- 2026-11-12: advisory: CVE-2026-120151 published; fixes released for versions 14.25, 15.20, 16.16, 17.12, and 18.7