CVE-2026-120064: high-severity vulnerability in PostgreSQL psqlODBC
psqlODBC does not validate column numbers and row indexes in binding and descriptor functions
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.3%
Several psqlODBC entry points use an application-supplied column number or row index as an array index without validating it. SQLBindCol with a column number above 32767 wraps the binding count negative and a later copy runs off the array. A negative SQL_DESC_COUNT on an application row descriptor unbinds columns at negative indexes. SQLColAttribute with a very large column number uses a negative index. SQLSetPos(SQL_ADD) does not check the row number against the rowset size. An application that forwards untrusted column or row numbers exposes its process to out-of-bounds reads and writes. Versions before psqlODBC 18.00.0006 are affected.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products
PostgreSQL · psqlODBCRelated CVEs — PostgreSQL psqlODBC
In the same product, most dangerous first.
CVE-2026-120062HIGHpsqlODBC SQL injection through SQLSpecialColumns table and schema namesEPSS 0.4%CVE-2026-120067MEDIUMpsqlODBC stack buffer overflow copying ctid and oid values for updatable cursorsEPSS 0.3%CVE-2026-120061HIGHpsqlODBC ODBC escape parser stack buffer overflowEPSS 0.3%CVE-2026-120065HIGHpsqlODBC does not escape a server-supplied column name in its updatable-cursor queriesEPSS 0.3%CVE-2026-120063MEDIUMpsqlODBC stack buffer overflow when quoting long schema and table namesEPSS 0.3%CVE-2026-120059MEDIUMpsqlODBC uses a server-supplied column name as a format stringEPSS 0.3%