Live › vulnerability › CVE-2026-120064
Several psqlODBC driver functions use an application-supplied column number or row index as an array index without checking it. An application that passes untrusted values into these calls can have its process read and write memory out of bounds.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 19:24 UTC. All times on this page are UTC.
Applications that use the psqlODBC driver and forward untrusted column numbers or row indexes into the driver's binding, attribute or positioning calls are exposed. Applications that only pass fixed, internally generated column and row numbers are less exposed. unknown whether the sources list other conditions.
No product ranges from the sources yet.
18.00.0006 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-120064")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.