Quick answers
- Is CVE-2026-120143 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120143 being exploited in the wild.
- How severe is CVE-2026-120143?
- 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-120143?
- 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-120143 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-120143?
- 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 is a use-after-free in PostgreSQL's trigger function implementation, specifically when a cursor is used over a transition table. An authenticated attacker with object creation privileges can exploit this to execute arbitrary code as the OS user running the database server. The attack requires local authentication (PR:L) but no user interaction, and no special network setup beyond the ability to submit SQL commands.
Affected products
- PostgreSQL PostgreSQL before 18.7, 17.12, 16.16, 15.20, 14.25
Timeline
- 2026-11-12: disclosed
- 2026-11-12: patched