Quick answers
- Is CVE-2026-120150 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120150 being exploited in the wild.
- How severe is CVE-2026-120150?
- High severity, with a CVSS score of 8.8, published 12 November 2026.
- Which products and versions are affected?
- PostgreSQL before 18.7, 17.12, 16.16, 15.20, 14.25.
- Is there a fix for CVE-2026-120150?
- Yes: fixed in PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120150 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-120150?
- 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 18.7, 17.12, 16.16, 15.20, 14.25
Technical details
A use-after-free vulnerability exists in PostgreSQL's expanded-record domain validation logic. When repeated domain checks are performed over a composite type, a dangling memory-context pointer is reused, leading to memory corruption. The vulnerability requires authenticated database access and object creation privileges to exploit; attackers can trigger arbitrary code execution as the OS user running the database process.
Affected products
- PostgreSQL PostgreSQL before 18.7, 17.12, 16.16, 15.20, 14.25
Timeline
- 2026-11-12: disclosed: CVE-2026-120150 published
- 2026-11-12: patched: PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25 released