Quick answers
- Is CVE-2026-120139 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120139 being exploited in the wild.
- How severe is CVE-2026-120139?
- 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, 18.7.
- Is there a fix for CVE-2026-120139?
- 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-120139 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120139?
- 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
An integer wraparound vulnerability in PostgreSQL's in-memory tuple-size calculations allows an authenticated database user to trigger arbitrary code execution as the OS user running the database. The flaw is triggered via oversized tuple data and requires database login privileges but no elevated rights. This is a privilege escalation from database user to OS-level execution.
Affected products
- PostgreSQL PostgreSQL before 14.25, 15.20, 16.16, 17.12, 18.7
Timeline
- 2026-11-12: disclosed
- 2026-11-12: patched