CVE-2026-120064: Out-of-bounds Read

Published Nov 2, 2026
·
Updated

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 SQLDESCCOUNT on an application row descriptor unbinds columns at negative indexes. SQLColAttribute with a very large column number uses a negative index. SQLSetPos(SQLADD) 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 Software

11 affected componentsFixes available
debian/psqlodbc*
debian/psqlodbc*
debian/psqlodbc*
debian/psqlodbc<=1:13.02.0000-2, <=1:17.00.0004-2, <=1:18.00.0005-1
1:18.00.0006-1
ubuntu/psqlodbc*
ubuntu/psqlodbc*
ubuntu/psqlodbc*
ubuntu/psqlodbc*
ubuntu/psqlodbc*
ubuntu/psqlodbc*
ubuntu/psqlodbc*

Event History

Nov 2, 2026
CVE Published
via NVD·07:18 PM
Data Sourced
via NVD·07:18 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·07:18 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which applications are realistically exposed to this issue?

Applications using psqlODBC before 18.00.0006 are exposed when they pass untrusted or insufficiently validated column numbers or row indexes into affected ODBC entry points. The vulnerable operations include SQLBindCol, SQLColAttribute, SQLSetPos(SQL_ADD), and descriptor handling involving SQL_DESC_COUNT.

2

What does an attacker need to exploit it?

An attacker needs a way to influence column numbers, row indexes, or an application row descriptor count supplied by the application to psqlODBC. Exploitation depends on the application forwarding those values without validating their range.

3

Are standard psqlODBC deployments affected by default?

The data does not indicate that ordinary use alone triggers the flaw. Exposure requires application-controlled values that are out of range, such as a SQLBindCol column number above 32767, a negative SQL_DESC_COUNT, a very large SQLColAttribute column number, or a SQLSetPos(SQL_ADD) row number beyond the rowset size.

4

What can be done if upgrading is not immediately possible?

Validate all column-number and row-index inputs before passing them to psqlODBC, and reject negative, excessively large, or rowset-out-of-range values. In particular, prevent SQLBindCol column values above 32767 and ensure SQLSetPos(SQL_ADD) row numbers do not exceed the rowset size.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203