# CVE-2026-120062: psqlODBC SQL injection in SQLSpecialColumns

Source: https://junglewise.ai/threats/cve-2026-120062-sqlspecialcolumns-in-psqlodbc-splices-the-table-and-schema-names  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-02. Updated: 2026-11-02  
License: CC BY 4.0 with a link back

CVE-2026-120062 · Severity: high · CVSS 7.5 · Published 2026-11-02

psqlODBC is a database connector that allows applications to query PostgreSQL servers. The SQLSpecialColumns function fails to escape table and schema names before using them in SQL queries, allowing an attacker to inject arbitrary SQL commands. An application that accepts user-supplied table or schema names and passes them to this function could allow unauthorized database access or data manipulation with the privileges of the database connection.

Technologies: [PostgreSQL psqlODBC](https://junglewise.ai/threats/technologies/postgresql-psqlodbc). Vendors: [PostgreSQL](https://junglewise.ai/threats/vendors/postgresql).

## 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

## References

- [https://github.com/postgresql-interfaces/psqlodbc/security/advisories/GHSA-gg8f-fx3w-rj33](https://github.com/postgresql-interfaces/psqlodbc/security/advisories/GHSA-gg8f-fx3w-rj33)

## Related threats

- [psqlODBC stack buffer overflow in updatable cursor handling](https://junglewise.ai/threats/cve-2026-120067-for-updatable-cursors-which-are-enabled-by-default-psqlodbc-adds)
- [psqlODBC insecure log file handling on Unix systems](https://junglewise.ai/threats/cve-2026-120066-on-unix-like-systems-when-logging-is-enabled-psqlodbc-creates)
- [psqlODBC SQL injection in row identification for updatable cursors](https://junglewise.ai/threats/cve-2026-120065-for-an-updatable-cursor-over-a-table-without-oids-that-has-an)
- [PostgreSQL psqlODBC array index validation buffer overflow](https://junglewise.ai/threats/cve-2026-120064-several-psqlodbc-entry-points-use-an-application-supplied-column)
- [psqlODBC stack buffer overflow in schema/table name quoting](https://junglewise.ai/threats/cve-2026-120063-when-psqlodbc-quotes-a-schema-or-table-name-into-a-128-byte)