Quick answers
- Is CVE-2026-120067 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120067 being exploited in the wild.
- How severe is CVE-2026-120067?
- Medium severity, with a CVSS score of 5.9, published 2 November 2026.
- Which products and versions are affected?
- PostgreSQL psqlODBC before 18.00.0006.
- Is there a fix for CVE-2026-120067?
- Yes: fixed in psqlODBC 18.00.0006. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120067 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120067?
- Check whether you run PostgreSQL psqlODBC 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: psqlODBC 18.00.0006
Technical details
The vulnerability is a stack buffer overflow in psqlODBC's handling of updatable cursors. When processing queries, the driver adds hidden ctid and oid columns and copies their values into a 32-byte stack buffer without validating that the server-provided length does not exceed the buffer size. An untrusted PostgreSQL server or any database user able to create views with custom ctid columns can send values of 32 bytes or more, overwriting adjacent stack memory. Applications built with _FORTIFY_SOURCE will abort; others risk code execution or process crash.
Affected products
- PostgreSQL psqlODBC before 18.00.0006
Timeline
- 2026-11-02: disclosed