Quick answers
- Is CVE-2026-120146 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120146 being exploited in the wild.
- How severe is CVE-2026-120146?
- Medium severity, with a CVSS score of 4.3, 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-120146?
- 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-120146 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-120146?
- 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
The REASSIGN OWNED command fails to enforce SET and CREATEDB privilege checks that are correctly enforced by the equivalent ALTER ... OWNER commands. A role granted INHERIT but not SET privilege can use REASSIGN OWNED to transfer objects to other roles, and database ownership can be reassigned without the CREATEDB privilege. This is a privilege escalation through inconsistent authorization enforcement between command variants.
Affected products
- PostgreSQL PostgreSQL before 14.25, 15.20, 16.16, 17.12, 18.7
Timeline
- 2026-11-12: disclosed: CVE-2026-120146 published