Quick answers
- Is CVE-2026-120060 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120060 being exploited in the wild.
- How severe is CVE-2026-120060?
- 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-120060?
- Yes: fixed in psqlODBC 18.00.0006. Until then: Ensure PostgreSQL server connections use SSL/TLS with certificate verification enabled to prevent untrusted servers from reaching the client driver. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120060 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-120060?
- 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
Ensure PostgreSQL server connections use SSL/TLS with certificate verification enabled to prevent untrusted servers from reaching the client driver.
Technical details
The driver trusts server-supplied row counts and field lengths in three places without proper validation. SQLBulkOperations performs integer underflow when subtracting a server-supplied row count, SQLStatistics iterates unbounded over server-supplied index key counts, and bytea octal decoding reads beyond truncated escape sequence boundaries. An attacker controlling an untrusted PostgreSQL server (or performing network interception without SSL verification) can trigger out-of-bounds memory reads or client crashes.
Affected products
- PostgreSQL psqlODBC before 18.00.0006
Timeline
- 2026-11-02: disclosed