# CVE-2026-120064: PostgreSQL psqlODBC array index validation buffer overflow

Source: https://junglewise.ai/threats/cve-2026-120064-several-psqlodbc-entry-points-use-an-application-supplied-column  
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-120064 · Severity: high · CVSS 7.5 · Published 2026-11-02

psqlODBC is a driver that allows applications to connect to PostgreSQL databases through the ODBC interface. Multiple functions in psqlODBC fail to validate column numbers and row indexes supplied by applications before using them as array indices, allowing out-of-bounds memory access. An application that forwards untrusted column or row numbers could be exploited to read or write memory and crash the process or execute arbitrary code.

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

## Quick answers

**Is CVE-2026-120064 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-120064 being exploited in the wild.

**How severe is CVE-2026-120064?** 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-120064?** 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-120064 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-120064?** 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

Multiple ODBC entry points (SQLBindCol, SQLColAttribute, SQLSetPos) accept application-supplied column or row numbers without validation, leading to out-of-bounds array access. SQLBindCol with column numbers above 32767 causes integer wrap to negative values; negative SQL_DESC_COUNT unbinds at negative indexes; SQLSetPos(SQL_ADD) does not bounds-check row numbers. The vulnerability allows remote or local code execution if an application forwards untrusted input to these functions.

## Affected products

- PostgreSQL psqlODBC before 18.00.0006

## Timeline

- 2026-11-02: disclosed

## References

- [https://github.com/postgresql-interfaces/psqlodbc/security/advisories/GHSA-7pq2-q7mj-ph8c](https://github.com/postgresql-interfaces/psqlodbc/security/advisories/GHSA-7pq2-q7mj-ph8c)

## 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)
- [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)
- [psqlODBC SQL injection in SQLSpecialColumns](https://junglewise.ai/threats/cve-2026-120062-sqlspecialcolumns-in-psqlodbc-splices-the-table-and-schema-names)