Live › vulnerability › CVE-2026-120065
psqlODBC, the PostgreSQL ODBC driver, builds queries by wrapping an auto-increment column name in double quotes without escaping embedded double quotes. A database user who can create a table with a crafted column name can change the SQL the driver runs under the application's privileges, including which rows an UPDATE or DELETE touches.
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 using psqlODBC with updatable cursors over tables that have an auto-increment int4 column and no OIDs. Exposure is greater where database users can create tables the application reads, or where the driver connects to a server not trusted under current SSL settings. Systems that do not use updatable cursors or do not run untrusted table creation can deprioritize this.
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.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-120065")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.