Quick answers
- Is CVE-2026-120062 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120062 being exploited in the wild.
- How severe is CVE-2026-120062?
- High severity, with a CVSS score of 7.5, published 2 November 2026.
- Which products and versions are affected?
- PostgreSQL psqlODBC before 18.00.0006.
- Is there a fix for CVE-2026-120062?
- 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-120062 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120062?
- 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
SQLSpecialColumns in psqlODBC performs unsafe string splicing of table and schema names into SQL catalog queries without proper escaping, while other catalog functions do escape these parameters. An attacker can exploit this by providing a crafted table or schema name containing SQL metacharacters to execute arbitrary SQL with the connection's privileges. This is a SQL injection vulnerability that requires the application to pass untrusted input to SQLSpecialColumns.
Affected products
- PostgreSQL psqlODBC before 18.00.0006
Timeline
- 2026-11-02: disclosed