Quick answers
- Is CVE-2026-120142 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120142 being exploited in the wild.
- How severe is CVE-2026-120142?
- High severity, with a CVSS score of 8.8, published 12 November 2026.
- Which products and versions are affected?
- PostgreSQL 17.0 through 17.11, 18.0 through 18.6.
- Is there a fix for CVE-2026-120142?
- 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-120142 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-120142?
- 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
The vulnerability exploits type confusion in PostgreSQL's anonymous RECORD type handling when row types have dropped attributes in identical positions but with differing widths or alignments. An authenticated attacker with object creation privileges can construct specially crafted RECORD types to trigger memory safety issues and achieve arbitrary code execution within the database process. The vulnerability affects PostgreSQL 17 and 18; versions before 17 are unaffected.
Affected products
- PostgreSQL PostgreSQL 17.0 through 17.11, 18.0 through 18.6
Timeline
- 2026-11-12: disclosed
- 2026-11-12: patched