CVE-2026-120064: psqlODBC does not validate column numbers and row indexes in binding and descriptor functions
PostgreSQL · psqlODBC
Vendor fix available · Affected: PostgreSQL psqlODBC · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 28% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- PostgreSQL · psqlODBCbefore 18.00.0006
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- PostgreSQL
- Published
- November 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-120064 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.