Quick answers
- Is CVE-2026-120063 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120063 being exploited in the wild.
- How severe is CVE-2026-120063?
- 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-120063?
- 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-120063 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120063?
- 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 quoting logic for schema and table names. A 128-byte stack buffer's length check is insufficient, allowing writes up to two bytes past the buffer end when processing long names extracted from application SQL text. The overflow also occurs during @@IDENTITY rewrites where column names from the server can write one byte past the buffer. An attacker can trigger this via untrusted SQL text passed to the driver.
Affected products
- PostgreSQL psqlODBC before 18.00.0006
Timeline
- 2026-11-02: disclosed