CVE-2026-120065: SQL Injection
For an updatable cursor over a table without OIDs that has an auto-increment int4 column, psqlODBC uses that column to identify rows. It places the column's name, as reported by the server, between double quotes in its keyset queries and in the WHERE clause of its positioned SELECT, UPDATE, and DELETE statements, without doubling any double quote in the name. A column name that contains a double quote therefore changes the SQL that the driver runs with the application's privileges, including which rows a positioned UPDATE or DELETE affects. Any database user who can create a table that the application reads with an updatable cursor can choose such a name, and so can a server not trusted under current SSL settings. Versions before psqlODBC 18.00.0006 are affected.
Affected Software
Event History
Frequently Asked Questions
Who can exploit this vulnerability?
A database user who can create a table that the application reads through an updatable cursor can supply a column name containing a double quote. A server that is not trusted under the current SSL settings can also provide a malicious column name.
What application behavior is required for exploitation?
The application must use an updatable cursor on a table without OIDs that has an auto-increment int4 column. The vulnerable driver then uses that column name in keyset and positioned SELECT, UPDATE, or DELETE queries.
What is the potential impact?
Injected SQL runs with the application's database privileges. An attacker can alter the SQL used by positioned UPDATE or DELETE statements, including changing which rows those statements affect.
Which versions need to be remediated?
psqlODBC versions before 18.00.0006 are affected. Upgrade to 18.00.0006 or a later version.