Quick answers
- Is CVE-2026-116335 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116335 being exploited in the wild.
- How severe is CVE-2026-116335?
- 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, and 18.7.
- Is there a fix for CVE-2026-116335?
- 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-116335 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-116335?
- 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 vulnerability arises from type confusion in PostgreSQL's operator commutator and negator links, exploitable by linking operators with different result types or creating inconsistent reciprocal links. An authenticated attacker with object creation capabilities can trigger arbitrary code execution as the database system user. The issue affects the core server component and requires authentication and object creation privileges.
Affected products
- PostgreSQL PostgreSQL before 14.25, 15.20, 16.16, 17.12, and 18.7
Timeline
- 2026-11-12: disclosed
- 2026-11-12: patched